Method and apparatus for slice aware multiple radio access technology resource sharing

Abstract

Embodiments of the present disclosure provide a method and apparatus for slice aware sharing of multiple radio access technology resources. A method performed by an access network node comprises: transmitting a first message comprising a first slice list to a core network node; and receiving a second message including the second slice list from the core network node. At least one of the first slice list and / or the second slice list comprises at least a first slice configured with radio resources scheduled from radio resources shared by at least the first RAT and the second RAT. According to embodiments of the present disclosure, slice level information may be communicated for MRSS. Namely, information regarding which slice is using / is capable of using the shared resource may be communicated between different network nodes, particularly between an access network node and a core network node.

Description

TECHNICAL FIELD

[0001] Various example embodiments of the present disclosure relate generally to the art of communications, and particularly to methods and apparatus for slice-aware multiple radio access technology resource sharing. BACKGROUND

[0002] In a communication network, many techniques such as slicing, resource sharing are employed to improve the usage efficiency of radio resources.

[0003] Network slicing is a logical network that groups network capabilities and network characteristics into a service that can be exposed to network users or used internally by network management. It is a key enabler in 5G (Fifth Generation) SA (Stand-alone Networking) to support different services using the same underlying mobile network infrastructure.

[0004] Multiple radio resource sharing, such as multi-RAT (Radio Access Technology) spectrum sharing (MRSS) allowing different RATs (such as NR (New Radio) and 6G (Sixth Generation)) cells to share the same subcarrier(s) dynamically adapting to traffic requirements. For example, the decision to provide orthogonal resources to the 6G and 5G air interfaces is typically given at the scale of transmission time intervals (TTIs).

[0005] While intra-G (intra-generation) radio slicing is known, there is no method to guide multi-RAT resource management in a way that is aware of the rest of the slicing framework. SUMMARY

[0006] This summary is provided to introduce some aspects of the subject matter, which will be further described below. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used in limiting the scope of the claimed subject matter.

[0007] Particular aspects of the present disclosure and their embodiments can provide solutions to these or other challenges. Various embodiments addressing one or more of the problems disclosed herein are set forth herein. Particular methods and apparatus for slice-aware multiple radio access technology resource sharing are provided.

[0008] A first aspect of the present disclosure provides a method performed by an access network node. The method comprises: sending, to a core network node, a first message comprising a first list of slices; and receiving, from the core network node, a second message comprising a second list of slices. At least one of the first list of slices and / or the second list of slices comprises at least a first slice configured with radio resources scheduled from radio resources shared by at least a first radio access technology, RAT, and a second RAT.

[0009] In an example embodiment of the disclosure, the first message further comprises at least a first indication for the first slice, the first indication relating to a capability to support a radio resource scheduled from radio resources shared by at least the first RAT and the second RAT. Alternatively or in addition, the first indication is comprised in a first network slice selection assistance information, NSSAI, for the first slice.

[0010] In an example embodiment of the disclosure, the first indication is a slice differentiator, SD, value or a slice / service type, SST, value. Alternatively or in addition, the first indication is comprised in a radio access network, RAN, configuration update message.

[0011] In an example embodiment of the disclosure, the first slice list is supported by an access network node and the first message is a setup request message. The second slice list is supported by a core network node and the second message is a setup response message.

[0012] In an example embodiment of the disclosure, the first slice list is requested by an access network node and the first message is a registration request message. The second slice list is configured by a core network node and the second message is a registration accept message.

[0013] In an example embodiment of the disclosure, the first slice list is requested by an access network node and the first message is a session setup request message. The second slice list is allocated by a core network node and the second message is a session setup response message. The second message further comprises at least one radio access technology / frequency selection priority, RFSP, index associated with the second slice list.

[0014] In an example embodiment of the disclosure, the first slice list is received by an access network node from a terminal device. The terminal device comprises a user equipment, UE.

[0015] In an example embodiment of the disclosure, the shared radio resource is dynamically scheduled to the first RAT and / or the second RAT by a scheduling node in the access network. The first message further comprises a second indication of a presence of the scheduling node in the access network.

[0016] In an example embodiment of the disclosure, the method further comprises: creating a profile for at least the first slice; sending the profile to a neighboring access network node; coordinating the neighboring access network node to schedule a radio resource shared by at least the first RAT and the second RAT; the profile comprising at least one of: inter-RAT parameters for the first RAT and the second RAT; slice bit rate limits per RAT type; capabilities for a terminal device to establish a radio resource control, RRC; and / or parameters for balancing traffic load between the first RAT and the second RAT.

[0017] In example embodiments of the present disclosure, the first RAT is a fifth generation RAT, and the second RAT is a sixth generation RAT. The access network node comprises: a base station, or a central unit, CU, of a base station. The core network node comprises: an entity for managing access and / or mobility.

[0018] A second aspect of the present disclosure provides a method performed by a core network node. The method comprises: receiving, from an access network node, a first message comprising a first list of slices; and sending, to the access network node, a second message comprising a second list of slices. At least one of the first list of slices and / or the second list of slices comprises: at least a first slice configured with radio resources scheduled from radio resources shared at least by a first radio access technology, RAT, and a second RAT.

[0019] In example embodiments of the present disclosure, the first message further comprises at least a first indication for the first slice, the first indication relating to a capability to support radio resources scheduled from radio resources shared at least by the first RAT and the second RAT. Alternatively or in addition, the first indication is comprised in first network slice selection assistance information, NSSAI, for the first slice.

[0020] In example embodiments of the present disclosure, the first indication is a slice differentiator, SD, value, or a slice / service type, SST, value. Alternatively or in addition, the first indication is comprised in a radio access network, RAN, configuration update message.

[0021] In example embodiments of the present disclosure, the first list of slices is supported by the access network node, and the first message is a setup request message. The second list of slices is supported by the core network node, and the second message is a setup response message.

[0022] In example embodiments of the present disclosure, the first list of slices is requested by the access network node, and the first message is a registration request message. The second list of slices is configured by the core network node, and the second message is a registration accept message.

[0023] In example embodiments of the present disclosure, the first list of slices is requested by the access network node, and the first message is a session setup request message. The second list of slices is allocated by the core network node, and the second message is a session setup response message. The second message further comprises: at least one RAT / frequency selection priority, RFSP, index associated with the second list of slices.

[0024] In example embodiments of the present disclosure, the shared radio resources are dynamically scheduled to the first RAT and / or the second RAT by a scheduling node in the access network. The first message further comprises: a second indication for a presence of the scheduling node in the access network.

[0025] A third aspect of the present disclosure provides a method performed by a scheduling node in an access network. The method comprises: receiving a slice configuration request indicating cross-RAT coordination; estimating radio resource requirements for different RATs; balancing the radio resource requirements for different RATs; reporting, to a core network node, the estimated and / or balanced radio resource requirements for different RATs; and scheduling radio resources shared by different RATs based at least on the estimated and / or balanced radio resource requirements for different RATs.

[0026] A fourth aspect of the present disclosure provides a method performed by a terminal device. The method comprises: sending, to an access network node, a third message comprising a first slice list; and receiving, from the access network node, a fourth message comprising a second slice list. At least one of the first slice list and / or the second slice list comprises at least a first slice configured with radio resources scheduled from radio resources shared by at least a first radio access technology, RAT, and a second RAT.

[0027] In exemplary embodiments of the present disclosure, the first slice list is requested by the terminal device, and the third message is a registration request message or a session establishment request message. The second slice list is configured or allocated by the core network node and / or the access network node, and the fourth message is a registration accept message or a session establishment response message.

[0028] A fifth aspect of the present disclosure provides an apparatus for an access network node. The apparatus for an access network node comprises: at least one processor; and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus for an access network node at least to perform the method according to any embodiment in the above first aspect.

[0029] A sixth aspect of the present disclosure provides an apparatus for a core network node. The apparatus for a core network node comprises: at least one processor; and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus for a core network node at least to perform the method according to any embodiment in the above second aspect.

[0030] A seventh aspect of the present disclosure provides an apparatus for a scheduling node in an access network. The apparatus for a scheduling node in an access network comprises: at least one processor; and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus for a scheduling node in an access network at least to perform the method according to any embodiment in the above third aspect.

[0031] An eighth aspect of the disclosure provides an apparatus for a terminal device. The apparatus for a terminal device comprises at least one processor; and at least one memory including computer program codes. The at least one memory and the computer program codes are configured to, with the at least one processor, cause the apparatus for a terminal device at least to perform the method according to any of the embodiments in the fourth aspect above.

[0032] A ninth aspect of the disclosure provides a computer readable storage medium storing instructions that, when executed by at least one processor of a network node or a terminal device, cause the at least one processor of the network node or the terminal device to perform the method according to any of the embodiments mentioned in the first aspect, the second aspect, the third aspect, the fourth aspect above.

[0033] According to embodiments of the disclosure, exemplary embodiments of the disclosure propose a mechanism that provides specific mechanisms for slice-aware multiple radio access technology resource sharing.

[0034] According to embodiments of the disclosure, slice level information that can be conveyed for MRSS execution includes, but is not limited to, slice type, resource allocation policy, and bandwidth. That is, information about which slice is using / able to use the shared resource can be conveyed between different network nodes, more specifically, between an access network node and a core network node. BRIEF DESCRIPTION OF DRAWINGS

[0035] The above and other aspects, features, and advantages of various embodiments of the disclosure will become more fully apparent from the following detailed description, by way of example, in conjunction with the accompanying drawings, in which like reference numerals or letters are used to indicate like components (or parts, elements etc.) throughout the specification. The drawings are for purposes of illustrating the exemplary embodiments of the disclosure and are not necessarily drawn to scale, wherein:

[0036] Figure 1 is a diagram illustrating exemplary E2E orchestration and assurance with slices.

[0037] Figure 2 is a diagram illustrating exemplary resource sharing between different RATs.

[0038] Figure 3 is a high level diagram illustrating cross-RAT slices according to exemplary embodiments of the disclosure.

[0039] Figure 4A is a flowchart of a method for execution by an access network node according to embodiments of the disclosure.

[0040] Figure 4B is a flowchart illustrating Figure 4A additional steps of

[0041] Figure 5 is a flowchart of a method for execution by a core network node according to embodiments of the disclosure.

[0042] Figure 6 is a flowchart of a method for execution by a scheduling node in an access network according to embodiments of the disclosure.

[0043] Figure 7 is a flowchart of a method for execution by a terminal device according to embodiments of the disclosure.

[0044] Figure 8 is an exemplary diagram illustrating signaling for MRSS capability and UE registration according to embodiments of the disclosure.

[0045] Figure 9 is an exemplary diagram illustrating signaling for PDU establishment over MRSS slice according to embodiments of the disclosure.

[0046] Figure 10 is a diagram illustrating exemplary cooperation between base stations of different RATs according to embodiments of the disclosure.

[0047] Figure 11 is a diagram illustrating two examples of lower level (radio) entities that would need to be aware of slice level information (policy) when performing carrier / resource sharing decisions.

[0048] Figure 12 is a block diagram illustrating an exemplary structure for an access network node according to exemplary embodiments of the disclosure.

[0049] Figure 13 is a block diagram illustrating an exemplary structure for a core network node according to exemplary embodiments of the disclosure.

[0050] Figure 14 is a block diagram illustrating an exemplary structure for a scheduling node in an access network according to exemplary embodiments of the disclosure.

[0051] Figure 15 is a block diagram illustrating an exemplary structure for a terminal device according to exemplary embodiments of the disclosure.

[0052] Figure 16 is a block diagram illustrating an apparatus / computer readable storage medium according to embodiments of the disclosure.

[0053] Figure 17 is a block diagram illustrating exemplary apparatus elements for an access network node according to embodiments of the disclosure, suitable for executing the methods.

[0054] Figure 18is a block diagram of exemplary apparatus units for a core network node suitable for performing the methods according to embodiments of the present disclosure.

[0055] Figure 19 is a block diagram of exemplary apparatus units for a scheduling node in an access network suitable for performing the methods according to embodiments of the present disclosure.

[0056] Figure 20 is a block diagram of exemplary apparatus units for a terminal device suitable for performing the methods according to embodiments of the present disclosure. DETAILED DESCRIPTION

[0057] Embodiments of the present disclosure are described in detail with reference to the attached drawings. It is to be understood that the embodiments are discussed only for a better understanding of the present disclosure, and are not limiting of the scope of the present disclosure. The features, advantages, and characteristics described herein can be combined in any manner in one or more embodiments.

[0058] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the application, unless a different meaning is clearly given and / or is implied from the context. The steps of any methods disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or is implicit from the context. Any feature of any of the embodiments disclosed herein can be applied to any other embodiment, where suitable.

[0059] As used herein, the term “network” or “communication network” refers to a network following any suitable communication standard, such as the Internet or any wireless network. For example, the wireless communication standard can include WLAN (Wireless Local Area Network), New Radio (NR), Long Term Evolution (LTE), LTE-Advanced, 5G NR, 6G, etc. In the following description, the terms “network” and “system” can be used interchangeably.

[0060] The term “node / network node” refers to a computing device, or a computing entity, or a computing function, or any other device (physical or virtual) in a communication network. For example, a node in a network can comprise a base station (BS), an access point (AP), or any suitable device in a wireless communication network. A BS can be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a next Generation Node B (gNode B or gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low power node (such as femto, pico, etc.). In addition, a node can comprise other core network nodes such as an Access and Mobility Management Function AMF, a Session Management Function SMF, a User Plane Function UPF, a Mobile Management Entity AMF, or a Serving Gateway S-GW, etc. It can also refer to emerging open network architecture involving disaggregation of RAN, such as variants based on O-RAN (such as O-DU, O-RU, and intelligent RAN controllers). O-RAN refers to Open Radio Access Network, O-DU refers to O-RAN Distributed Unit, and O-RU refers to O-RAN Radio Unit.

[0061] The term “terminal device” refers to any terminal device that can access a communication network and receive services therefrom. By way of example but not limitation, a terminal device refers to a mobile terminal, a user equipment (UE), a non-AP device (such as a non-AP base station (STA)), or other suitable device. A terminal device can include, but is not limited to, a mobile phone, a cellular phone, a smartphone, a wearable device, a vehicle-mounted wireless terminal device, a vehicle, etc.

[0062] As one example, a terminal device can represent a device configured to communicate in accordance with one or more communication standards promulgated by any standards organization, such as the 3rd Generation Partnership Project (3GPP).

[0063] As another example, in an Internet of Things (IoT) scenario, a terminal device can represent a machine or other device that performs monitoring and / or measurement, and transmits a result of the monitoring and / or measurement, such as to another terminal device and / or a network device. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g., refrigerators, televisions), personal wearable devices such as watches, etc. In other scenarios, a terminal device can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0064] It should be understood that, although the terms“first” and“second” etc. can be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element without departing from the scope of the example embodiments. As used herein, the term“and / or” includes any and all combinations of one or more of the associated listed terms.

[0065] As used herein,“at least one of ,”“at least one of ,” and the like, wherein the list of two or more elements is

[0066] Figure 1 is a diagram illustrating example E2E orchestration and assurance with slicing.

[0067] In Figure 1 E2E refers to end-to-end. 4G refers to fourth generation. NSA refers to non-standalone. FWA refers to fixed wireless access. IoT refers to Internet of Things. SD-WAN refers to software-defined wide area network. MPLS refers to multiprotocol label switching. VPN refers to virtual private network. IETF refers to Internet Engineering Task Force.

[0068] A network slice is a logical network grouping network capabilities and network characteristics into a service that can be exposed to network users or used internally by network management. It is a key enabler in 5G (fifth generation) SA (standalone) to support different services using the same underlying mobile network infrastructure. The verticals of a slice (i.e., a slice customer) can customize the network according to the needs of the service. Isolation between slices ensures that the operation of one slice does not affect other slices. 6G (sixth generation) networks are expected to continue and expand the use of slicing.

[0069] 3GPP (Third Generation Partnership Project) has defined six standardized slice / service types in Rel (Release) 18 (eMBB (enhanced mobile broadband), URLLC (ultra-reliable and low-latency communication), MioT (massive Internet of Things), V2X (vehicle-to-everything), HMTC (high-performance machine type communication), and HDLLC (high data rate & low latency communication)). Slices can be subscription-based or service-based dynamic slicing [3GPP Technical Specification (TS) 23.501].

[0070] Figure 2 is a diagram illustrating example resource sharing between different RATs.

[0071] In Figure 2 HW refers to hardware. SW refers to software. FR1 refers to frequency range 1.

[0072] Multi-RAT (Radio Access Technology) Spectrum Sharing (MRSS) is a key feature for the migration to 6G, as it allows NR (New Radio) and 6G cells to share the same carrier(s) that dynamically adapt to the traffic requirements. For example, the decision to provide orthogonal resources to the 6G and 5G air interfaces is typically made at the scale of transmission time intervals (TTIs). In some MRSS-based 6G deployments, the following elements are envisioned to be common to both RATs and can be dynamically shared by 5G and 6G cells:

[0073] • OAM (Operation, Administration, and Maintenance)

[0074] • CN (Core Network) Network Functions (NFs)

[0075] • Transport (backhaul, midhaul, fronthaul)

[0076] • RAN (Radio Access Network) (BB / BF (Baseband / Frequency Radio))

[0077] • Spectrum, i.e., partially or fully overlapping carriers.

[0078] Slice and multi-RAT sharing techniques are discussed by 3GPP and others. While intra-generation (intra-generation) radio slices are known, there is no standardized approach to steer multi-RAT resource management in a way that is aware of the rest of the slice framework. At this time, all 6G slice frameworks assume dedicated spectrum for legacy and new RATs, and there is no suitable mechanism to extend the concept of sharing network resources to the carrier level. One of the technical challenges is the fact that slices and MRSS target different time granularities and levels of traffic aggregation.

[0079] The proposed embodiments of the present disclosure complement the radio access network (RAN) slicing by extending their capabilities to different RAT use cases, such as for 5G-6G, and can also be applicable to multi-rate and multi-vendor radio slicing. In particular, the exemplary embodiments of the present disclosure can enhance slice resource allocation by enabling cross-slice usage across different air interfaces.

[0080] Figure 3 is a high-level diagram illustrating cross-RAT slicing according to exemplary embodiments of the present disclosure.

[0081] Such exemplary embodiments can introduce cross-RAT slicing based on a common SA (standalone networking) core, slice-aware multi-RAT spectrum sharing, and encompass cases where 5G and 6G are provided by the same vendor, as well as cases where they come from different vendors.

[0082] Embodiments of the present disclosure can relate to cross-RAT awareness of RAN slices, RRM policies between slices, resource isolation between slices, and access control. More specifically, embodiments of the present disclosure can propose steps and signaling to define one (or more) 6G slice(s) associated with specific policies (rate, latency limits, etc.) that will provide non-real-time input to the MRSS algorithm that decides in real-time the resource partitioning between NR and 6G cells, which extends the key principles outlined in TS 38.300 [Section 16.3] for the implementation of network slices in NG-RAN to scenarios where NR and 6G share the same carrier.

[0083] At a high level, embodiments of the present disclosure can propose mechanisms to convey slice-level information to the MRSS decision level (with / without MRSS mediator) that then uses this information to guide the cross-RAT resource partitioning in an appropriate and timely manner.

[0084] Figure 4A is a flowchart of a method for execution by an access network node according to embodiments of the present disclosure.

[0085] As shown in Figure 4A The method 400 executed by the access network node comprises a step S402 of sending, to a core network node, a first message comprising a first list of slices, and a step S404 of receiving, from the core network node, a second message comprising a second list of slices. At least one of the first list of slices and / or the second list of slices comprises at least a first slice configured with radio resources scheduled from radio resources shared at least by a first radio access technology, RAT, and a second RAT.

[0086] According to embodiments of the present disclosure, slice-level information can be conveyed for MRSS. That is, information about which slice is / are using / able to use the shared resources is conveyed between different network nodes, in particular between the access network node and the core network node.

[0087] In exemplary embodiments of the present disclosure, the first message further comprises at least a first indication for the first slice, the first indication relating to a capability to support radio resources scheduled from radio resources shared at least by the first RAT and the second RAT. Alternatively or in addition, the first indication is comprised in a first network slice selection assistance information, NSSAI, for the first slice.

[0088] According to embodiments of the present disclosure, an indication relating to a capability of a slice to support cross-RAT resource sharing can be used, in particular in the NSSAI. A network node in the communication network will be able to understand the capability of the slice directly from such an indication.

[0089] In example embodiments of the present disclosure, the first indication is a slice differentiator, SD, value or a slice / service type, SST, value. Alternatively or additionally, the first indication is included in a radio access network, RAN, configuration update message.

[0090] According to embodiments of the present disclosure, the SD value or SST value can be used. Then, the adjustment required for the existing message and / or interface for conveying the MRSS slice information can be reduced. It should be appreciated that for such indication, other new / adjusted information elements in other messages, such as the RAN configuration update message of the NGAP protocol or its subsequent protocol, can also be used.

[0091] In example embodiments of the present disclosure, the first slice list is supported by the access network node, and the first message is a setup request message. The second slice list is supported by the core network node, and the second message is a setup response message.

[0092] In example embodiments of the present disclosure, the first slice list is requested by the access network node, and the first message is a registration request message. The second slice list is configured by the core network node, and the second message is a registration accept message.

[0093] In example embodiments of the present disclosure, the first slice list is requested by the access network node, and the first message is a session setup request message. The second slice list is allocated by the core network node, and the second message is a session setup response message. The second message further includes at least one radio access technology / frequency selection priority, RFSP, index associated with the second slice list.

[0094] According to embodiments of the present disclosure, the message about the MRSS slice can be conveyed in various procedures, such as a setup procedure, a registration procedure, and / or a session setup procedure.

[0095] In example embodiments of the present disclosure, the first slice list is received by the access network node from a terminal device. The terminal device includes a user equipment, UE.

[0096] In example embodiments of the present disclosure, the shared radio resource is dynamically scheduled to the first RAT and / or the second RAT by a scheduling node in the access network. The first message further includes a second indication of the presence of the scheduling node in the access network.

[0097] According to embodiments of the present disclosure, the access network node can indicate the core network node with the capability of dynamically adjusting the shared radio resource (i.e., the MRSS slice support capability).

[0098] Figure 4B is a flowchart showing additional steps of Figure 4A .

[0099] In an example embodiment of the disclosure, the method further comprises: step S406, creating a profile for at least the first slice; step S408, sending the profile to the neighboring access network node; and step S410, coordinating the neighboring access network node to schedule radio resources shared by at least the first RAT and the second RAT. The profile comprises at least one of:

[0100] inter-RAT parameters for the first RAT and the second RAT, which can be related to, for example, a level of cross-carrier scheduling, MAC partitioning, use of split bearers, control of transmission spectrum characteristics, general or dedicated DCI (Downlink Control Information), primary cell group, secondary cell group and backup cell group;

[0101] slice bitrate limits per RAT type;

[0102] parameters for establishing capabilities of a terminal device for radio resource control, RRC; and / or

[0103] parameters for balancing traffic load between the first RAT and the second RAT.

[0104] The access network node can be for the first RAT, and the neighboring access network node can be for the second RAT. The second RAT can be different from the first RAT. In the case of a dual scheduler (optional -1) as shown in Figure 11 the profile can be sent via an interface between distributed units (DUs). That is, according to an embodiment of the disclosure, coordination between different access network nodes can be used. The coordination can be direct or via another separate scheduling node.

[0105] In an example embodiment of the disclosure, the first RAT is a fifth generation RAT, and the second RAT is a sixth generation RAT. The access network node comprises: a base station, or a central unit, CU, of a base station. The core network node comprises: an entity for managing access and / or mobility.

[0106] According to an embodiment of the disclosure, the proposed method can be particularly suitable for the upcoming 5G to 6G migration. However, it should be noted that the proposed method can also be applied between any other types of different RATs.

[0107] Figure 5 is a flowchart of a method for execution by a core network node according to an embodiment of the disclosure.

[0108] As Figure 5As shown in the middle, the method 500 performed by the core network node comprises: receiving (S502), from the access network node, a first message comprising a first list of slices; and sending (S504), to the access network node, a second message comprising a second list of slices. At least one of the first list of slices and / or the second list of slices comprises at least a first slice configured with radio resources scheduled from radio resources shared by at least a first radio access technology, RAT, and a second RAT.

[0109] In an example embodiment of the disclosure, the first message further comprises at least a first indication for the first slice, the first indication relating to a capability to support radio resources scheduled from radio resources shared by at least the first RAT and the second RAT. Alternatively or in addition, the first indication is comprised in first network slice selection assistance information, NSSAI, for the first slice.

[0110] In an example embodiment of the disclosure, the first indication is a slice differentiator, SD, value, or a slice / service type, SST, value. Alternatively or in addition, the first indication is comprised in a radio access network, RAN, configuration update message.

[0111] In an example embodiment of the disclosure, the first list of slices is supported by the access network node, and the first message is a setup request message. The second list of slices is supported by the core network node, and the second message is a setup response message.

[0112] In an example embodiment of the disclosure, the first list of slices is requested by the access network node, and the first message is a registration request message. The second list of slices is configured by the core network node, and the second message is a registration accept message.

[0113] In an example embodiment of the disclosure, the first list of slices is requested by the access network node, and the first message is a session setup request message. The second list of slices is allocated by the core network node, and the second message is a session setup response message. The second message further comprises at least one RAT / frequency selection priority, RFSP, index associated with the second list of slices.

[0114] In an example embodiment of the disclosure, the shared radio resources are dynamically scheduled to the first RAT and / or the second RAT by a scheduling node in the access network. The first message further comprises a second indication for a presence of the scheduling node in the access network.

[0115] Figure 6 is a flowchart of a method for performing by a scheduling node in an access network according to an embodiment of the disclosure.

[0116] As Figure 6As shown in FIG. 6, the method 600 performed by the scheduling node in the access network comprises: step S602, receiving a slice configuration request indicating cross-RAT coordination; step S604, estimating radio resource requirements of different RATs; step S606, balancing radio resource requirements of different RATs; step S608, reporting the estimated and / or balanced radio resource requirements of different RATs to the core network node; and step S610, scheduling radio resources shared by different RATs based at least on the estimated and / or balanced radio resource requirements of different RATs.

[0117] According to embodiments of the present disclosure, with the scheduling node in the access network having information about slices in different RATs, multi-RAT management can be performed in a way that is aware of the rest of the slice framework.

[0118] Figure 7 is a flowchart of a method for performing by a terminal device according to embodiments of the present disclosure.

[0119] As Figure 7 As shown in FIG. 7, the method 700 performed by the terminal device comprises: step S702, sending a third message comprising a first slice list to the access network node; and step S704, receiving a fourth message comprising a second slice list from the access network node. At least one of the first slice list and / or the second slice list comprises: at least a first slice configured with radio resources scheduled from radio resources shared by at least a first radio access technology, RAT, and a second RAT.

[0120] In exemplary embodiments of the present disclosure, the first slice list is requested by the terminal device, and the third message is a registration request message or a session establishment request message. The second slice list is configured or allocated by the core network node and / or the access network node, and the fourth message is a registration accept message or a session establishment response message.

[0121] According to embodiments of the present disclosure, the terminal device can also have information about MRSS slices. The terminal device can have more information about how the shared resources are arranged for its own communication, and manage its data transmission or reception accordingly. Communication efficiency can be improved. In addition, which information the terminal device has can also depend on the RAT. For example, a 5G UE can not be aware of MRSS, and it can be designed to be transparent to such devices. A 6G UE can be made aware that a 6G cell uses a shared carrier. The UE or both (5G and 6G) UEs can be aware of the slices. As another example, there can be a case that a given 6G slice requested by a UE prefers not to use an MRSS carrier if another carrier in a dedicated frequency band is available.

[0122] Figure 8is an exemplary diagram illustrating signaling for MRSS capability and UE registration according to embodiments of the disclosure.

[0123] A MRSS slice is a slice that can share radio resources with another MRSS slice of a different RAT. For example, a 6G slice can share radio resources with a 5G slice. This sharing (i.e., a particular way of partitioning the shared radio resources (time-frequency)) can be static or dynamic. Furthermore, a slice can use resources in 5G format and 6G format at the same time.

[0124] Steps 1, 2, 3, 5, 22, 23 are at least related to MRSS information.

[0125] In Figure 8 AUSF refers to authentication server function, UDM refers to unified data management. PCF refers to policy control function. UPF refers to user plane function.

[0126] As shown in Figure 8 In step 1, the (R)AN node (such as a base station) sends a NGPA setup request (indicating capabilities for MRSS slice support, and / or a list of supported MRSS slices) to the AMF.

[0127] In step 2, the (R)AN node receives a NGPA setup response (indicating capabilities for MRSS slice support, and / or a list of supported MRSS slices) from the AMF.

[0128] In step 3, the UE sends a registration request (including a requested MRSS_NSSAI).

[0129] In step 4, the (R)AN node can select an AMF.

[0130] In step 5, the (R)AN node can send a registration request (including a requested MRSS_NSSAI) to the AMF.

[0131] In step 6, the AMF can send an identity request to the (R)AN node.

[0132] In step 7, the (R)AN node can send an identity request to the UE.

[0133] In step 8, the UE can send an identity response to the (R)AN node.

[0134] In step 9, the (R)AN node can send an identity response to the AMF.

[0135] In step 10, the AMF selects an AUSF.

[0136] In step 11, an authentication / security procedure is performed.

[0137] In step 12-21, a UMD selection and registration procedure is performed.

[0138] In step 22, the AMF sends a registration accept (including configured MRSS_NSSAI) to the (R)AN node.

[0139] In step 23, the (R)AN node sends a registration accept (including configured MRSS_NSSAI) to the UE.

[0140] In step 23b, a UE policy association establishment procedure is performed between at least the AMF and the PCF.

[0141] In step 24, the AMF verifies UE entitlement and slice availability.

[0142] In step 25, the UE sends a registration complete to the (R)AN node.

[0143] In step 25b, the (R)AN node sends a registration complete to the AMF.

[0144] In steps 26-27, the UDM is updated.

[0145] In step 28, network slice specific authentication and authorization is performed.

[0146] Figure 9 is an exemplary diagram illustrating signaling for PDU establishment over MRSS slices according to embodiments of the present disclosure.

[0147] In Figure 9 , SMF refers to a session management function. CU-UP refers to a central unit user plane. DRB refers to a dynamic resource block. PDCP / SAP refers to a packet data convergence protocol / service access point. MAC / MRRM refers to a medium access control / multi-radio resource management.

[0148] As shown in Figure 9 , in step 29, the UE sends a PDU session establishment request (including requested MRSS_NSSAI) to the (R)AN-1, which can be, for example, the (R)AN node in Figure 9 .

[0149] In step 30, the (R)AN-1 node sends a PDU session establishment request (including requested MRSS_NSSAI) to the AMF, which can be, for example, the AMF in Figure 8 .

[0150] In step 31, the AMF selects an SMF.

[0151] In step 32, the AMF sends an Nsmf_PDUSession_CreateSMContext request to the selected SMF.

[0152] In step 33, a subscription retrieval procedure is performed.

[0153] In step 34, the SMF sends an Nsmf_PDUSession_CreateSMContext response to the AMF.

[0154] In step 35, a PDU session authentication / authorization procedure is performed.

[0155] In step 36, an N4 session establishment procedure is performed.

[0156] In step 37, the SMF sends a Namf_Communication_N1N2Transfer to the AMF.

[0157] In step 38, the AMF sends a Namf_Communication_N1N2Transfer Ack to the SMF.

[0158] In step 39, the AMF sends a N2 PDU session request (including MRSS_NSSAI, RFSP index assigned to the PDU session) to the (R)AN-1 node.

[0159] The (R)AN-1 node then performs CU-UP selection, DRB allocation procedure, and performs PDCP / SAP and MAC / MRRM configuration.

[0160] In step 40, the (R)AN-1 node sends an XnAP message with MRSS profile to one or more (R)AN-2 nodes, which can be neighboring RAN nodes of the (R)AN-1 node. Then, in step 40b, a confirmation message can be sent from RAN2 back to RAN1 to ensure the MRSS slice configuration is accepted.

[0161] In step 41, the (R)AN-1 node sends a PDU session establishment resource setup (including MRSS_NASSI assigned to the PDU session) to the UE.

[0162] In step 42, the (R)AN-1 node sends a PDU session response to the AMF.

[0163] In step 43, the UE sends uplink data.

[0164] In step 44, the AMF sends an Nsmf_PDUSession_UpdateSMContext request to the SMF.

[0165] In step 45, a session modification procedure is performed.

[0166] In step 46, the UE receives downlink data.

[0167] In step 47, the SMF sends an Nsmf_PDUSession_UpdateSMContext response to the AMF.

[0168] As shown in Figure 8 , 9 , during NG setup, the RAN and the AMF / 6GMM (Access and Mobility Management Function / 6G Mobility Management) exchange their supported NSSAI (Network Slice Selection Assistance Information) list via NG Setup Request and NG Setup Response, see Figure 8 . This NGAP (Next Generation Application Protocol) setup procedure signaling needs to be updated to include an indication of the RAN node's MRSS slice capability. An indicator needs to be introduced in the NGAP setup message by which the RAN informs the core network about the presence of a MRSS scheduler in the RAN.

[0169] The way to encode the MRSS support into S-NSSAI is to introduce a new IE (Information Element) for MRSS slice support in the RAN Configuration Update message of the NGAP protocol [TS 38.413].

[0170] MRSS indication (where it is NSSAI, SD / SST, etc.) can also contain information of allowed applications on the slice. For example, a standard NSSAI can be augmented with an indicator showing that the slice is MRSS capable and supports multi-RAT (5G and 6G) radios. MRSS slice is a slice that is aware that it operates on MRSS carriers and supports dynamic resource pooling across different air interfaces. That is, a cooperative scheduler (distributed or centralized) can quickly adapt to different traffic situations within the limits set by the slice level measurements. It is the presence of 6G UEs that makes the spectrum to be shared across RATs, UE subscription and RAN capability indicate that MRSS is supported by the access network node. This is indicated by defining a slice differentiator (SD) value for MRSS slices. Alternatively, a new slice / slice type (SST) value can be defined, but it should be noted that the SST field in S-NNAI is only 8 bits long, while SD is 24 bits. If S-NSSAI contains information about MRSS support (by a newly defined SD value) and there is a MRSS scheduler in the RAN, the MRSS scheduler will be updated with MRSS profile information when the slice is established.

[0171] When a slice is established (typically at PDU session establishment), the gNB or CU-CP (Central Unit - Control Plane) for the gNB creates a MRSS profile based on information collected from the CN. The MRSS profile information is shared with MRSS peer RATs over XnAP-signaling [TS 38.423] (step 40 in Figure 9

[0172] For example, the MRSS profile can include:

[0173] • augmented NSSAI, STT and / or SD for MRSS capability,

[0174] • inter-RAT parameters for 5G and 6G radios,

[0175] • UE slice maximum bit rate per RAT type,

[0176] • necessary UE capabilities for establishing RRC (Radio Resource Control) according to TS 38.306,

[0177] • cross-RAT RRMPolicyRatio that directs load balancing between the involved RATs.

[0178] ​The network can / may provide the UE with a Network Slice Selection Policy (NSSP) as part of the URSP rule to use a MRSS slice for use cases benefiting from MRRS slices (see TS 23.503, clause 6.6.2). The use of MRSS slices can also be left to the decision of the network side policy.

[0179] When establishing a PDU session using a specific MRSS network slice instance (S-NSSAI (Single Network Slice Selection Assistance Information) with MRSS support), the AMF / 6GMM can provide an explicit MRSS-NSSAI RFSP (RAT / Frequency Selection Priority) index (according to TS 23.501, clause 5.3.4) to guide the RAN node to use MRSS slice capabilities. If the CN policy changes, the MRSS-NSSAI RFSP index can be used to dynamically reallocate the use of MRSS resources (6G and / or 5G).

[0180] Figure 10 Figure is an illustration of exemplary cooperation between base stations of different RATs according to embodiments of the present disclosure.

[0181] The signaling as shown in Figure 10 may be associated with step 40 in Figure 9 .

[0182] In Figure 10 , RU stands for Resource Unit. eCPRI stands for Enhanced Common Public Radio Interface.

[0183] In Figure 10 focus is on the split scheduler, as a joint 5G-6G scheduler (e.g., in a single vendor scenario) is considered an extension and can rely on proprietary interfaces and vendor-specific rules to ensure that complete and up-to-date information about the resource needs of each RAT sharing the carrier aggregation is exchanged in near real-time.

[0184] Furthermore, direct coordination across CUs is assumed. That is, the functionality of the mediator as shown in Figure 11 is distributed among the CUs. The MRSS profile can be exchanged over XnAP. The 6G CU and the 5G CU can communicate and coordinate the use of MRSS. New MRSS slice parameters / information elements can be transferred in messages (XnAP messages) between the two. Thus, for example, 1) an “enhanced 5G CU” (with the mediator functionality integrated) can support MRSS slice message extensions, or 2) the “mediator” functionality can be applied between the mentioned 5G CU and 6G CU.

[0185] In one embodiment, steps 0-7 in the above Figure 10 may be the following:

[0186] 0) Differentiated slice configuration requests (e.g., from the 6G side) from core network nodes (such as AMF / 6GMM) to 6G CU;

[0187] 1) Requests for cross-RAT coordination, from 6G CU to 5G CU;

[0188] 2) Requests to estimate radio resource requirements, from CU to DU;

[0189] 3) The estimated requirements for notification, from DU to CU;

[0190] 4) Cross-CU negotiation / coordination;

[0191] 5) Response NW (AMF / 6GMM);

[0192] 6) Scheduling rules / policies, from CU to DU;

[0193] 7) The UE was notified (not) that it had accepted the notification.

[0194] This can be generalized to scenarios with different layer divisions, such as when F1 (interface) is not present or is being utilized in 6G.

[0195] The above assumes that each CU aggregation comes from the demand of a dedicated (GBR (licensed bitrate)) slice.

[0196] Alternatively, indirect reconciliation can be achieved via a multi-RAT resource manager (MRRM). MRRM (not in Figure 10 (As described in the text) can reconcile Layer-2 interactions between 5G DU and 6G DU.

[0197] A direct DU-DU interface can also be considered for multi-vendor (MV) MRSS and is applicable. However, it is sufficient for slice coordination across CU-CP and associated signaling on F1_C (F1_control) or proprietary interfaces.

[0198] How each CU / DU estimates effective radio resource requirements can depend on the (scheduler) implementation.

[0199] In one embodiment, the estimated demand for each RAT can be based on a movement time window, such as 1 second or longer. MRSS resource partitioning decisions are expected to have a time granularity of no more than 100 ms. Optimized implementations can operate at the TTI (Transmission Time Interval) level.

[0200] In another embodiment, it can use AI / ML technology to predict the business needs of its own and / or peer schedulers based on customized models and previous iterations.

[0201] Different algorithms can also be used to ensure orthogonal allocations across vendors. Other embodiments of this disclosure may provide additional considerations and possible extensions.

[0202] For example, three rough classifications of the coordination of shared resources and the priority of slice aggregation requirements for each RAT might be provided:

[0203] o Key slice (highest priority)

[0204] ■ RAT (UL and DL) configurations for PHY (physical) signaling, general channels, and SRB (signaling radio bearer)

[0205] ■Static reservation plus a carrier-configurable deregistration timer is a direct implementation example.

[0206] o Differentiated slices (high priority)

[0207] ■ Provide dynamic resource reservation / differentiation for slices carrying GBR services

[0208] ■ Semi-static configuration and specification (reservation / prioritization) of radio resources for each RAT

[0209] o Plain section (to the best of my ability)

[0210] ■All other (non-GBR)

[0211] ■ Use the remaining resources allocated to each RAT

[0212] ■ Grouping and aggregation can be based on the existing SST (Slice / Service Type) type (TS 23.501) and the MRSS indicator proposed in the above embodiments of this disclosure.

[0213] The embodiments disclosed herein can be applied to both CSPs (Communication Service Providers) and private networks that deploy 5G and 6G cells sharing (multiple) the same component carriers.

[0214] The embodiments disclosed herein can be applied to enhance / improve 3GPP TS (or any other relevant standard).

[0215] Figure 11 This is a diagram illustrating two examples of lower-level (radio) entities that will need to be aware of slice-level information (policy) when making carrier / resource sharing decisions.

[0216] exist Figure 11 In Chinese, MAC refers to Media Access Control.

[0217] Multi-vendor support can be proposed and implemented using RAN slice templates via extended XnAP signaling (Xn Application Protocol signaling). These templates contain a generic, minimal set of configuration parameters (also known as "MRSS profiles") required to establish an MRSS scheduler for multiple RAT slices, allowing the involved RANs to select and allocate appropriate resources for the MRSS slices. In other examples, Figure 11 It can also represent a standardized O-RAN Y interface (or similar) that can be used to manage and control the deployment of slices in the RAN.

[0218] MRSS profiles can be derived from UE capabilities as defined in TS 38.300. They include UE capabilities for different RATs (i.e., inter-RAT capabilities for 5G and 6G in TS 38.306), load balancing information between different schedulers (extending the existing TS28.541 RMPolicy to multi-RAT use, with cross-RATRMPolicyRatio IoC (information object class) indicating new necessary parameters for load balancing), and PDU (protocol data unit) sessions related to slice information and QoS (quality of service) flow class (multiple) QoS profiles.

[0219] Multi-RAT Spectrum Sharing (MRSS) is a key feature for a smooth network migration from 5G to 6G, enabling protection of customer investments and superior day-1 6G coverage and capacity. Network slicing is a concept introduced by 5G SA (Standalone) to allow for differentiated treatment based on each customer's requirements.

[0220] Embodiments of this disclosure can allow for the efficient deployment and management of combining two concepts (MRSS, network slicing).

[0221] Embodiments of this disclosure can provide the necessary information, on both short and long timescales, enabling a RAT to dynamically and flexibly take precedence over other RATs.

[0222] For example, under high load conditions, 6G slices [with SLAs (Service Level Agreements) optimized for, for example, mobile robots or immersive video experiences] can take precedence over traditional default 5G slices [which serve eMBB services].

[0223] Embodiments of this disclosure enable public network aggregation NPN (non-public network) (PNI-NPN) use cases to share resources between public network operators and enterprises, as well as between enterprises.

[0224] Due to new AI / ML (Artificial Intelligence / Machine Learning) capabilities and specialized private NW (Network) deployment scenarios and use cases, the number and types of standardized and carrier-specific network slice (NS) instances are expected to increase. Therefore, embodiments of this disclosure can allow for other efficient uses of such slices.

[0225] Figure 12 This is a block diagram illustrating an exemplary structure for accessing a network node according to exemplary embodiments of the present disclosure.

[0226] like Figure 12 As shown, the apparatus 120 for accessing a network node includes: at least one processor 1202; and at least one memory 1204, including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus 120 for accessing a network node to at least perform the methods according to any of the above embodiments, such as... Figure 4A , 4B As shown in 8, 9, 10, and 11.

[0227] Figure 13 This is a block diagram illustrating an exemplary structure for a core network node according to exemplary embodiments of the present disclosure.

[0228] like Figure 13 As shown, the apparatus 130 for a core network node includes: at least one processor 1302; and at least one memory 1304, including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus 130 for the core network node to at least perform the methods according to any of the above embodiments, such as... Figure 5 , 8 As shown in 9, 10, and 11.

[0229] Figure 14 This is a block diagram illustrating an exemplary structure for a scheduling node in an access network according to exemplary embodiments of the present disclosure.

[0230] like Figure 14 As shown, the apparatus 140 for accessing a scheduling node in a network includes: at least one processor 1402; and at least one memory 1404, including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus 140 for accessing a scheduling node in a network to at least perform the methods according to any of the above embodiments, such as... Figure 6 , 8 As shown in 9, 10, and 11.

[0231] Figure 15This is a block diagram illustrating an exemplary structure for a terminal device according to exemplary embodiments of the present disclosure.

[0232] like Figure 15 As shown, the apparatus 150 for a terminal device includes: at least one processor 1502; and at least one memory 1504, including computer program code. The at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus 150 for the terminal device to at least perform the methods according to any of the above embodiments, such as... Figure 7 , 8 As shown in 9, 10, and 11.

[0233] Processors 1202, 1302, 1402, and 1502 can be any type of processing component, such as one or more microprocessors or microcontrollers, and other digital hardware, which may include digital signal processors (DSPs), application-specific digital logic, etc. Memory 1204, 1304, 1404, and 1504 can be any type of storage component, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc.

[0234] Figure 16 This is a block diagram illustrating an apparatus / computer-readable storage medium according to embodiments of the present disclosure.

[0235] like Figure 16 As shown, computer-readable storage medium 160 stores instructions 1601, which, when executed by at least one processor of a network node or terminal device, cause at least one processor of the network node or terminal device to perform a method according to any of the embodiments mentioned above, such as Figure 4A , 4B As shown in numbers 5, 6, 7, 8, 9, and 10.

[0236] Furthermore, this disclosure may also provide a carrier containing the computer programs / instructions mentioned above. The carrier is an electronic signal, an optical signal, a radio signal, or one of the aforementioned computer-readable storage media. Computer-readable storage media may be, for example, optical discs or electronic storage devices such as RAM (Random Access Memory), ROM (Read-Only Memory), flash memory, magnetic tape, CD-ROM, DVD, Blu-ray disc, etc.

[0237] Figure 17 This is a block diagram illustrating exemplary device units suitable for performing methods and for accessing network nodes, according to embodiments of the present disclosure.

[0238] like Figure 17As shown, the access network node 170 may include: a sending unit 1702 configured to send a first message including a first slice list to a core network node; and a receiving unit 1704 configured to receive a second message including a second slice list from the core network node. At least one of the first slice list and / or the second slice list includes: at least a first slice configured with radio resources, which are scheduled from radio resources shared at least by a first radio access technology (RAT) and a second RAT.

[0239] In an exemplary embodiment of this disclosure, the access network node 170 is also configured to perform methods according to any of the embodiments mentioned above, such as Figure 4A , 4B As shown in 8, 9, 10, and 11.

[0240] Figure 18 This is a block diagram illustrating exemplary device units for a core network node suitable for performing a method, according to embodiments of the present disclosure.

[0241] like Figure 18 As shown, the core network node 180 may include: a receiving unit 1802 configured to receive a first message including a first slice list from the core network node; and a sending unit 1804 configured to send a second message including a second slice list to the access network node. At least one of the first slice list and / or the second slice list includes: at least a first slice configured with radio resources, which are scheduled from radio resources shared by at least a first radio access technology (RAT) and a second RAT.

[0242] In exemplary embodiments of this disclosure, the core network node 180 is also configured to perform methods according to any of the embodiments mentioned above, such as Figure 5 , 8 As shown in 9, 10, and 11.

[0243] Figure 19 This is a block diagram illustrating exemplary device units suitable for performing methods and for accessing scheduling nodes in a network, according to embodiments of the present disclosure.

[0244] like Figure 19As shown, the scheduling node 190 in the access network may include: a receiving unit 1902 configured to receive a slice configuration request indicating cross-RAT coordination; an estimation unit 1904 configured to estimate the radio resource requirements of different RATs; a balancing unit 1906 configured to balance the radio resource requirements of different RATs; a reporting unit 1908 configured to report the estimated and / or balanced radio resource requirements of different RATs to the core network node; and a scheduling unit 1910 configured to schedule radio resources shared by different RATs based at least on the estimated and / or balanced radio resource requirements of different RATs.

[0245] In an exemplary embodiment of this disclosure, the scheduling node 190 in the access network is also configured to perform methods according to any of the embodiments mentioned above, such as Figure 6 , 8 As shown in 9, 10, and 11.

[0246] Figure 20 This is a block diagram illustrating exemplary device units for a terminal device suitable for performing a method, according to embodiments of the present disclosure.

[0247] like Figure 20 As shown, the terminal device 200 may include: a sending unit 2002 configured to send a third message including a first slice list to an access network node; and a receiving unit 2004 configured to receive a fourth message including a second slice list from the access network node. At least one of the first slice list and / or the second slice list includes: at least a first slice configured with radio resources, which are scheduled from radio resources shared at least by a first radio access technology (RAT) and a second RAT.

[0248] In exemplary embodiments of this disclosure, the terminal device 200 is also configured to perform methods according to any of the embodiments mentioned above, such as Figure 7 , 8 As shown in 9, 10, and 11.

[0249] The term “unit” may have the conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuit systems, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, such as those described herein.

[0250] As used in this application, the term "circuit system" may refer to one or more, or all of the following:

[0251] (a) Hardware circuit implementation only (such as implementation using only analog and / or digital circuit systems) and

[0252] (b) A combination of hardware circuitry and software, such as (if applicable):

[0253] (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and

[0254] (ii) Any portion of a hardware processor(s) having software (including a plurality of digital signal processors(s), software, and a plurality of memories(s), which work together to enable a device(s) (such as a mobile phone or a server) to perform various functions) and

[0255] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when software is not required to operate.

[0256] The definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit system" also covers implementations of hardware circuitry or processors (or processors in general) or portions thereof and their accompanying software and / or firmware. For instance, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular networks, or other computing or networking devices.

[0257] Using these units, the device can be configured with any kind of computing and storage resources, without requiring a fixed processor or memory, and can be deployed from at least one node / device / entity / device associated with the communication system. Virtualization and network computing technologies (such as cloud computing) can also be introduced to improve the efficiency of network resource utilization and network flexibility.

[0258] The techniques described herein can be implemented by various components, such that the means for implementing one or more functions of the corresponding apparatus described in the embodiments includes not only components of the prior art, but also components for implementing one or more functions of the corresponding apparatus described in the embodiments, and may include separate components for each individual function, or components that can be configured to perform two or more functions. For example, these techniques can be implemented by hardware (one or more means), firmware (one or more means), software (one or more modules / units), or a combination thereof. For firmware or software, it can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described herein.

[0259] In certain embodiments, some or all of the functions described herein may be provided by a processing circuitry system that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-transient computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuitry system without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of these specific embodiments, the processing circuitry system may be configured to perform the described functions regardless of whether instructions stored on a non-transient computer-readable storage medium are executed. The benefits provided by such functions are not limited to individual processing circuitry or other components of the computing device, but are generally enjoyed by the computing device as a whole and / or by end users and wireless networks.

[0260] The term “non-transient” as used in this article refers to the limitation on the medium itself (i.e., tangible, not a signal), rather than the limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0261] As described in the exemplary embodiments above in this disclosure, the embodiments herein offer numerous advantages. According to embodiments of this disclosure, exemplary embodiments of this disclosure propose a mechanism for providing a specific process for sharing resources of multiple radio access technologies for slice awareness.

[0262] It should be understood that the above embodiments are for illustrative purposes only and not for limitation. This disclosure may be practiced in other ways than those specifically set forth herein without departing from its essential characteristics. All changes to these embodiments without departing from the meaning of the appended claims and their equivalents are intended to be included herein.

[0263] The following references may be incorporated into this paper in their entirety by reference.

[0264] 3GPP TS23.501, V19.0.0 (2024-06) [Section 5.15];

[0265] 3GPP TS 38.300, V18.1.0 (2024-03) [Section 16.3];

[0266] 3GPP TS 38.306, V18.1.0(2024-03);

[0267] 3GPP TS28.541, V18.7.0 (2024-03) [Sections 4.3.37, 5.3.95, 6.3.23];

[0268] 3GPP TS 38.413, V18.2.0(2024-06);

[0269] 3GPP TS 38.423, V18.2.0(2024-06);

[0270] 3GPP TS23.503, V19.0.0(2024-06);

[0271] 3GPP TS28.530, V18.0.0(2023-12);

[0272] 3GPP TS29.536, V18.6.0(2024-06);

[0273] 3GPP TS28.202, V18.0.0(2024-04);

[0274] O-RAN (Open Radio Access Network) Slicing Architecture 12.0, version R003, expands upon the O-RAN O1 interface to support RAN slice subnet provisioning, the E2 interface for RRM (Radio Resource Management) policy configuration and performance monitoring, and the O-CU (O-RAN Central Unit) and O-DU (O-RAN Distributed Unit) functions.

[0275] On September 14, 2023, the IETF (Internet Engineering Task Force) proposed "A Framework for Network Slices in Networks Built from IETF Technologies" (draft-ietf-teas-ietf-network-slices-25), which defines network slicing services on networks deployed using technologies owned by the IETF (IP (Internet Protocol), MPLS (Multiprotocol Label Switching), etc.).

[0276] Abbreviation Explanation

[0277] E2E end-to-end

[0278] 4G fourth generation

[0279] NSA Non-Standalone Networking

[0280] FWA Fixed Wireless Access

[0281] IoT (Internet of Things)

[0282] SD-WAN (Software-Defined Wide Area Network)

[0283] MPLS (Multiprotocol Label Switching)

[0284] VPN (Virtual Private Network)

[0285] IETF Internet Engineering Task Force

[0286] HW Hardware

[0287] SW software

[0288] FR1 Frequency range 1

[0289] 5G (Fifth Generation)

[0290] SA standalone networking

[0291] MRSS (Multiple Radio Access Technology) spectrum sharing

[0292] NR New Radio

[0293] 6G 6th generation

[0294] intra-G generation

[0295] eMBB Enhanced Mobile Broadband

[0296] URLLC: Ultra-Reliable and Low-Latency Communication

[0297] MioT (Massively Connected Internet of Things)

[0298] V2X vehicle-to-everything

[0299] HMTC High Performance Machine Type Communication

[0300] HDLLC High Data Rate and Low Latency Communication

[0301] OAM Operation, Management and Maintenance

[0302] CN NFs Core Network Functions

[0303] RAN (Radio Access Network)

[0304] BB / RF Baseband / Radio Frequency

[0305] PDU Protocol Data Unit

[0306] QoS (Quality of Service)

[0307] SLA (Service Level Agreement)

[0308] PNI-NPN Public Network Integration of Non-Public Networks

[0309] AI / ML Artificial Intelligence / Machine Learning

[0310] NW Network

[0311] NS network slices

[0312] NGAP Next Generation Application Protocol

[0313] AUSF Authentication Server Functionality

[0314] UDM Unified Data Management

[0315] PCF policy control function

[0316] UPF User Plane Functions

[0317] AMFs Access and Mobility Management Functions

[0318] 6GMMs 6G Mobility Management

[0319] CSP (Communication Service Provider)

[0320] 3GPP Third Generation Partnership Project

[0321] TS Technical Specifications

[0322] RRC Radio Resource Control

[0323] IE Information Elements

[0324] FR frequency range

[0325] Rel version

[0326] DL downlink

[0327] UL uplink

[0328] UE User Equipment

[0329] RB resource block

Claims

1. A method performed by an access network node, comprising: sending, to a core network node, a first message comprising a first list of slices; and receiving, from the core network node, a second message comprising a second list of slices; wherein at least one of the first list of slices and / or the second list of slices comprises: at least a first slice configured with radio resources scheduled from radio resources shared by at least a first radio access technology, RAT, and a second RAT.

2. The method of claim 1, wherein the first message further comprises at least a first indication for the first slice, the first indication relating to a capability to support radio resources scheduled from radio resources shared by at least the first RAT and the second RAT, and / or the first indication is comprised in a first network slice selection assistance information, NSSAI, for the first slice; and wherein the first indication is a slice differentiator, SD, value, or a slice / service type, SST, value, and / or wherein the first indication is comprised in a radio access network, RAN, configuration update message.

3. The method of any of claims 1-2, one of: wherein the first list of slices is supported by the access network node and the first message is a setup request message, and wherein the second list of slices is supported by the core network node and the second message is a setup response message; wherein the first list of slices is requested by the access network node and the first message is a registration request message, and wherein the second list of slices is configured by the core network node and the second message is a registration accept message; or wherein the first list of slices is requested by the access network node and the first message is a session setup request message, and the second list of slices is allocated by the core network node and the second message is a session setup response message; and the second message further comprises: at least one RAT / frequency selection priority, RFSP, index associated with the second list of slices.

4. The method of claim 3, wherein the first list of slices is received by the access network node from a terminal device; and wherein the terminal device comprises a user equipment, UE.

5. The method of claim 4, one or more of: wherein the shared radio resources are dynamically scheduled by a scheduling node in an access network to the first RAT and / or the second RAT, and the first message further comprises: a second indication for a presence of the scheduling node in an access network; wherein the method further comprises: creating a profile for at least the first slice, sending the profile to a neighboring access network node, coordinating the neighboring access network node to schedule radio resources shared by at least the first RAT and the second RAT, wherein the profile comprises at least one of: inter-RAT parameters for the first RAT and the second RAT, slice bit rate limits per RAT type, capabilities for establishing a radio resource control, RRC, terminal device, and / or parameters for balancing traffic load between the first RAT and the second RAT; or wherein the first RAT is a fifth generation RAT and the second RAT is a sixth generation RAT; and the access network node comprises: a base station, or a central unit, CU, of a base station; the core network node comprises: an entity for managing access and / or mobility.

6. A method performed by a core network node, comprising: receiving, from an access network node, a first message comprising a first list of slices; and sending, to the access network node, a second message comprising a second list of slices; wherein at least one of the first list of slices and / or the second list of slices comprises: at least a first slice configured with radio resources scheduled from radio resources shared by at least a first radio access technology, RAT, and a second RAT.

7. A method performed by a scheduling node in an access network, comprising: receiving a slice configuration request indicating cross-RAT coordination; estimating radio resource requirements for different RATs; balancing radio resource requirements for different RATs; reporting, to a core network node, the estimated and / or balanced radio resource requirements for different RATs; and scheduling the radio resources shared by the different RATs based at least on the estimated and / or balanced radio resource requirements for different RATs.

8. A method performed by a terminal device, comprising: sending, to the access network node, a third message including a first list of slices; and receiving, from the access network node, a fourth message comprising a second list of slices; wherein at least one of the first list of slices and / or the second list of slices comprises: at least a first slice configured with radio resources scheduled from radio resources shared by at least a first radio access technology, RAT, and a second RAT.

9. The method of claim 8, wherein the first list of slices is requested by the terminal device and the third message is a registration request message or a session establishment request message; and wherein the second list of slices is configured or allocated by a core network node and / or the access network node and the fourth message is a registration accept message or a session establishment response message.

10. An apparatus for communication, comprising: at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes configured to, with the at least one processor, cause the apparatus at least to perform the method according to any one of claims 1 to 9.

Images