Redundant user plane path coordination based on multiple terminal devices per terminal device group

Abstract

Embodiments of the present disclosure relate to user plane path coordination for multiple UEs per device. A network controller of a network system manages a plurality of network devices, receives status information from the network devices, where the status information includes: measurements provided to the network devices by terminal devices, and network device-specific measurements, determines a coordination policy based on the status information, and transmits the coordination policy to the network devices. The coordination strategy indicates a plurality of redundant user paths set by the network equipment for the terminal equipment; the coordination policy is provided to the network device.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly to methods, devices, apparatuses, and computer-readable storage media for redundant user plane path coordination based on multiple terminal devices per terminal device group. Background Art

[0002] 5G and Time-Sensitive Networking (TSN) technologies are key to future industrial communications: 5G for wireless connections and TSN for wired connections. According to 3GPP Rel-16, the 5GS functional architecture is integrated into the IEEE TSN network as a TSN bridge to support periodic deterministic time-sensitive Ethernet service flows. For industrial communications, especially for automatic control message transmission, ultra-reliability is critical. In TSN, ultra-reliability is provided by frame replication and reliability elimination (FRER) (802.1CB) for data flows through per-packet reliability mechanisms. This provides reliability by sending multiple copies of the same data packet on separate paths in the network. For the 5G+TSN case, FRER can be used in conjunction with 3GPP / 5G redundancy features, and end-to-end ultra-reliability is provided by applying FRER on the TSN and 5G domains.

[0003] In Rel-15, 3GPP has studied the solution of redundant user plane paths based on multiple terminal devices in each terminal device group. The static reliability group (RG) method (where RG establishment, management, and terminal device scheduling are semi-static) is introduced to ensure that terminal devices in the same terminal device group can be assigned different network devices for redundancy. However, the static RG method cannot well achieve effective redundancy and guarantee the ultra-reliability of TSN transmission in some cases. Summary of the invention

[0004] Generally speaking, example embodiments of the present disclosure provide solutions for redundant user plane path coordination.

[0005] In a first aspect, a network controller is provided. The network controller includes at least one processor and at least one memory storing instructions, and when the instructions are executed by the at least one processor, the network controller at least performs: receiving state information from a network device among a plurality of network devices managed by the network controller, the state information including: measurements provided by a terminal device to the network device, and measurements specific to the network device; determining a coordination strategy based on the state information, the coordination strategy indicating a plurality of redundant user paths set by the network device for the terminal device; and providing the coordination strategy to the network device.

[0006] In a second aspect, a network device is provided. The network device includes at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, causes the network device to at least perform: providing status information to a network controller, the network controller managing multiple network devices, the status information including measurements provided by a terminal device to the network device, and measurements specific to the network device; receiving a coordination policy from the network controller, the coordination policy indicating multiple redundant user paths set by the network device for the terminal device; and processing a redundant user plane configuration process of the terminal device based on the coordination policy, wherein the terminal device belongs to the network device.

[0007] In a third aspect, a terminal device is provided. The terminal device includes at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the terminal device to at least perform: providing status information from the terminal device to a network device, wherein the status information includes measurements of the terminal device, and sending a request for a protocol data unit (PDU) session to the network device, wherein the terminal device belongs to the network device.

[0008] In a fourth aspect, a method implemented at a network controller is provided. The method includes receiving, at a network controller of a network system, state information from a network device, the network controller managing a plurality of network devices, wherein the state information includes: measurements provided by a terminal device to the network device, and measurements specific to the network device; determining, by the network controller based on the state information, a coordination strategy indicating a plurality of redundant user paths set by the network device for the terminal device; and providing the coordination strategy to the network device.

[0009] In a fifth aspect, a method implemented at a network device is provided. The method includes: providing status information from the network device to a network controller, the network controller managing multiple network devices, wherein the status information includes: measurements provided by the terminal device to the network device, and measurements specific to the network device; receiving, at the network device, a coordination policy from the network controller, the coordination policy indicating multiple redundant user paths set by the network device for the terminal device; and processing a redundant user plane configuration process of the terminal device based on the coordination policy, wherein the terminal device belongs to the network device.

[0010] In a sixth aspect, a method implemented at a terminal device is provided, comprising: providing status information from the terminal device to a network device, wherein the status information comprises measurements of the terminal device; and sending a request for a protocol data unit (PDU) session to the network device, wherein the terminal device belongs to the network device.

[0011] In a seventh aspect, a non-transitory computer-readable medium comprising program instructions is provided, wherein the program instructions are used to cause an apparatus to at least execute a method according to any one of the fourth to sixth aspects above.

[0012] It should be understood that the summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0014] Figure 1 shows an example communication network in which embodiments of the present disclosure may be implemented;

[0015] Figure 2 A flow chart showing a process for redundant user plane path coordination according to some embodiments of the present disclosure is shown;

[0016] Figure 3 A flowchart of a method implemented at a network controller (eg, a radio intelligent controller RIC) according to some embodiments of the present disclosure is shown;

[0017] Figure 4 A flowchart of a method implemented at a network device according to some embodiments of the present disclosure is shown;

[0018] Figure 5 A flowchart of a method implemented at a terminal device according to some other embodiments of the present disclosure is shown;

[0019] Figure 6 A flow chart showing a method for implementing a coordination strategy for output reliability groups and diversity / redundancy at a network controller (eg, a wireless intelligent controller RIC);

[0020] Figure 7 shows a simplified block diagram of an apparatus suitable for implementing an embodiment of the present disclosure; and

[0021] Figure 8 A block diagram of an example computer-readable medium is shown in accordance with some embodiments of the present disclosure.

[0022] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0023] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art understand and implement the present disclosure without implying any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from the ways described below.

[0024] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0025] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of a person skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments (whether or not explicitly described).

[0026] It should be understood that although the terms "first" and "second" and the like may 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 element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0027] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms "include", "comprise", "have", "have", "include" and / or "comprising" when used herein specify the presence of features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0028] As used in this application, the term "circuitry" may refer to one, more than one, or all of the following:

[0029] (a) only hardware circuit implementation (e.g., only implementation in analog and / or digital circuits) and

[0030] (b) a combination of hardware circuitry and software, such as (where applicable):

[0031] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and

[0032] (ii) a hardware processor (including a digital signal processor) with software, software and any portion of memory that work together to enable a device such as a mobile phone or server to perform various functions) and

[0033] (c) Hardware circuits and / or processors (e.g., a microprocessor or a portion of a microprocessor) that require software (e.g., firmware) to operate, but where software is not required to operate, the software may not be present.

[0034] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also encompasses an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or its) accompanying software and / or firmware. The term circuitry also encompasses (for example and if applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0035] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal equipment and the network equipment in the communication network can be performed according to any suitable generation of communication protocols, including but not limited to the third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols and / or more. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there are of course future types of communication technologies and systems, which can be used to implement the present disclosure. It should not be regarded as limiting the scope of the present invention to the above-mentioned systems.

[0036] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services from it. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP) or a transmission and reception point (TRP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), an integrated access and backhaul (IAB) node, a relay, a low power node such as a femto, a pico, etc.

[0037] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS) or access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), USB dongles, smart devices, wireless client equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a target, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment, consumer electronic devices, devices operating on a commercial and / or industrial wireless network, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0038] The term "terminal device group" refers to any physical device equipped with one or more "terminal devices". A terminal device group that integrates multiple terminal devices can be independently connected to different network devices. The selection of different network devices for terminal devices in the same terminal device group is achieved through the concept of UE reliability groups (RGs) for terminal devices and for cells of network devices (see 3GPP TS23.501V16.12.0). By grouping the terminal devices in the terminal device group and the cells of the network devices in the network into more than one reliability group, the terminal devices in the same terminal device group can be assigned different network devices for redundancy.

[0039] As used herein, a network controller may be a RAN Intelligent Controller (RIC). RIC is a new virtualization function that adds RAN programmability to an existing or new RAN network. The near real-time RIC is connected to network devices / vCU+vDU via an E2 interface, supporting near real-time (10-100ms) data exchange between RIC and network devices, thereby enabling 10-100ms level RAN data collection and RRC control policy input through near real-time RIC. Near real-time RIC will provide enhanced capabilities for CU-CP through xAPP, E2 interface, and AI / ML capabilities. Similar to a centralized CU or RNC in WCDMA, the near real-time RIC will connect 100-1000 network devices / DUs, potentially playing the role of centrally coordinating the radio resources of network devices.

[0040] In Rel-15, 3GPP has studied the solution of redundant user plane paths based on multiple terminal devices in the same terminal device group. The static reliability group (RG) method (where RG establishment, management, and terminal device scheduling are semi-static) is introduced to ensure that terminal devices in the same terminal device group can be assigned different network devices for redundancy. However, the static RG method cannot well achieve effective redundancy and guarantee the ultra-reliability of TSN transmission in some cases.

[0041] According to an embodiment of the present disclosure, a solution for redundant user plane path coordination of multiple terminal devices based on each terminal device group is provided. In this solution, the dynamic characteristics of the RAN are taken into account, including, for example, dynamic cell load, changes in the number of terminal devices for each RG, terminal device mobility with different coverage, and changing radio channel conditions. Therefore, the provided solution can coordinate RG establishment, management, and selection via centralized coordination dynamically equipped with AI (artificial intelligence) inference capabilities.

[0042] In this solution, a new method for dynamic user plane redundancy optimization using centralized coordination and optional AI reasoning capabilities is introduced, and recommendations are made for the setup, management, and selection of reliability groups (RGs). By leveraging real-time status information from terminal devices and network devices, the optimization will provide the highest diversity / redundancy for all selected redundant paths. The optimization will provide the highest diversity / redundancy for other entities, such as non-real-time (Non-RTRIC), OAM, and / or 5G core network (5GC) for service level agreement (SLA) management.

[0043] The principles and embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Figure 1 , Figure 1 An example communication system 100 is shown in which embodiments of the present disclosure may be implemented.

[0044] The system 100 includes a network controller, in particular, a RIC 110. The system 100 includes a plurality of network devices, such as a network device 120 and a network device 125. The system 100 includes a core network 140. The system 100 also includes one or more terminal devices, such as terminal devices 130, 135. The terminal devices 130, 135 are in the same terminal device group 160. The system 100 also includes other nodes 150, such as a non-real-time RIC, an OAM and / or a 5G core network (5GC), etc.

[0045] RIC 110 is a centralized coordination function. It will subscribe and collect near real-time status information about network devices and terminal devices. In an example embodiment, these inputs will be maintained in a priority table in the RIC. Status information and static information are inputs for centralized coordination and optional AI inference. In some embodiments, RIC 110 has one or more AI / ML (machine learning) modules 111 and a coordination function module 112. AI / ML (machine learning) module 111 can perform AI inference functions, such as prediction of cell / RG load, terminal device mobility trajectory and / or channel quality of terminal devices. Coordination function module 112 can perform centralized coordination functions between different terminal devices and / or different network devices.

[0046] RIC 110 will subscribe to and collect new events from network devices, which will trigger the centralized coordination function and optional AI inference function to output the selection strategy of reliability group and diversity / redundancy. RIC 110 can provide diversity / redundancy to non-real-time RIC, OAM and / or 5GC. Diversity / redundancy is used for paths of terminal devices belonging to the same terminal device group.

[0047] The optimization principle of the centralized coordination function in RIC 110 can detect and allow the first PDU session establishment / modification request for the same terminal device group. By using the information maintained in the priority list, the optimization principle can detect and select a second or more number of RGs for the path with the highest diversity / redundancy compared to the previously selected / set RGs for the established path.

[0048] The RIC 110 may direct the serving network device to reject the PDU session establishment / modification procedure of the terminal device and instruct the terminal device to re-initiate the procedure via the recommended network device.

[0049] The RIC 110 may provide recommended connections in a setup policy to each network device (which provides a PDU session establishment event) based on some or all of the collected information.

[0050] The network device may have information of more than one terminal device, which indicates one or more terminal devices belonging to the same terminal device group, which is then reported by the network device to the RIC 110 as one of the inputs for centralized coordination and optional AI inference. The network device may report subscribed terminal devices and real-time status information of the network device to the RIC. The network device may report subscription events to the RIC and wait for instructions from the RIC for further processing.

[0051] It should be understood that the number of network devices and terminal devices is for illustration purposes only and does not imply any limitation. System 100 may include any suitable number of RICs, network devices, and terminal devices suitable for implementing embodiments of the present disclosure.

[0052] The communication in the communication system 100 can be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols of the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G) and the fifth generation (5G), such as wireless local area network communication protocols such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or developed in the future. In addition, the communication can utilize any appropriate wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM) and / or any other technology currently known or to be developed in the future.

[0053] Reference now Figure 2 , which illustrates a process 200 for redundant user plane path coordination according to an example embodiment of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 Process 200 is described. Process 200 may include the following: Figure 1 The terminal devices 130, 135 and the network devices 120, 125 are shown. It should be understood that although Figure 1 The process 200 is described in the communication system 100 of FIG. 1 , but the process can also be applied to other communication situations. It should also be understood that although the process for redundant user plane path coordination for terminal devices 130 and 135 is discussed, a similar process can be applied to any other terminal device for redundant user plane path coordination.

[0054] In process 200, at step 201, RIC 110 subscribes to status information provided by network device 120. At step 202, RIC 110 subscribes to status information reports provided by network device 125.

[0055] In some embodiments, the status information is at least one of near real-time status information of the terminal device, near real-time status information of the network device, and near real-time status information of the configuration of the reliability group.

[0056] In some embodiments, the status information of the terminal device includes: measurement information of the terminal device and / or connection information of the terminal device, such as the current RG, the current network device and the UE wireless channel measurement DL RSRP (reference signal received power), RSRQ (reference signal received quality), RSSI (received signal strength indication), device location, etc.

[0057] In some embodiments, the status information of the network device includes information on cell load, interference, etc.

[0058] In some embodiments, RIC 110 can read static information via O&M or A1 interface. Static information includes: configuration of reliability group, such as RG and its binding in network equipment and UPF (user plane function), connection weight between network equipment and UPF of different RG. Static information can also include geographical and physical parameters of network equipment and UPF, such as network equipment location, antenna location, antenna height, antenna angle, carrier, transmission settings, UPF location, etc.

[0059] In step 203, RIC 110 subscribes to PDU session establishment / modification related messages provided by network device 120. In some embodiments. In step 204, RIC 110 subscribes to PDU session establishment / modification related messages provided by network device 125. When network device 120 or 125 receives a PDU session establishment / modification related message related to terminal device 130, a related event will be sent to RIC 110. And the event can trigger centralized runtime RG management of terminal devices 130 and 135.

[0060] In steps 205 and 206, RIC 110 may continuously receive state information from network devices 120 and 125. In some embodiments, state information and static information will be stored in a priority list in the RIC.

[0061] In process 200 , terminal device 130 initiates a PDU session establishment / modification process and sends a request to CN 140 at step 207 .

[0062] In step 208, the PDU session establishment / modification is sent to the network device 120. In some embodiments, the network device 120 will first suspend all PDU session establishment / modification steps and extract the RG number, and then in step 209, send the detailed information of the event to the RIC 110.

[0063] After the RIC 110 receives the event, the RIC 110 may provide a coordination strategy to the network device 120 at step 210. The coordination strategy includes redundant user paths for the terminal device 130.

[0064] In some embodiments, RIC 110 checks the status information of terminal device 130. In the case where the path of terminal device 130 is the first path of the terminal device group, RIC 110 sends an instruction to start the PDU session establishment process to network device 120 by setting a policy. After network device 120 receives the instruction from RIC 110, network device 120 establishes a path for terminal device 130 and responds to CN 140 in step 211.

[0065] In process 200, terminal device 135 and terminal device 130 are in the same terminal device group 160. After terminal device 130 establishes a PDU session through the above steps, terminal device 135 initiates a PDU session establishment / modification process and sends a request to CN 140 in step 212.

[0066] In step 213, the PDU session establishment / modification is sent to the network device 120. In some embodiments, the network device 210 will first suspend all PDU session establishment / modification steps and extract the RG number, and then in step 214, send the detailed information of the event to the RIC 110.

[0067] After checking the event information, RIC 110 finds that this is not the first path of the terminal device group 160, so it triggers the centralized coordination operation in RIC 110. In some embodiments, the coordination function module 112 in RIC 110 takes the state information and static information as input, then selects the highest diversity / redundancy compared to the previous path, and then gives the recommended path as output.

[0068] In the case that the RG in the network device 125 is the best RG for the terminal device 135, the RIC will provide a switching strategy. In some embodiments, at step 215, the RIC 110 sends the resource reservation strategy as a request for the resource reservation process to the network device 125. At step 216, the network device 125 reserves resources for the terminal device 135 and sends a response to the RIC 110.

[0069] At step 217, RIC 110 sends a handover policy for the handover process to network device 120. Network device 120 responds to the handover to CN 140 at step 218. Network device 120 triggers the handover process of terminal device 135 according to the 3GPP standard.

[0070] At step 219, the PDU session establishment / modification is sent to the network device 125. In some embodiments, the network device 125 will first suspend all PDU session establishment / modification steps and extract the RG number, and then at step 220, send the detailed information of the event to the RIC 110.

[0071] After RIC 110 receives the event, RIC 110 may check the status information and find that the RG in network device 125 is the best RG in step 220. In step 221, RIC 110 sends an indication to network device 125 to start the PDU session establishment process. And after network device 125 receives the indication from RIC 110, network device 125 establishes a path for terminal device 135 and responds to CN 140 in step 222.

[0072] Figure 3 FIG. 3 is a flow chart showing an example method 300 implemented at a network controller (eg, a radio intelligent controller RIC) according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 The method 300 is described from the perspective of the RIC 110 .

[0073] In box 310, the RIC receives status information from at least one of the network devices, wherein the status information includes measurements of the terminal device and the network device. In box 320, the RIC determines a coordination strategy based on the status information, the coordination strategy including redundant user paths for the terminal device. The static information includes the configuration of the reliability group, such as RGs in the network device and UPF and their bindings, and the connection weights between network devices and UPFs of different RGs. The static information may also include geographical and physical parameters of the network device and UPF, such as network device location, antenna location, antenna height, antenna angle, carrier, transmission settings, UPF location, etc. In box 330, the RIC provides the coordination strategy to the network device.

[0074] In some embodiments, the RIC provides diversity / redundancy to the non-real-time RIC, OAM and / or 5GC, and the diversity / redundancy is calculated based on at least one of state information and static information.

[0075] In some embodiments, the RIC has subscribed to status information from network devices.

[0076] In some embodiments, the RIC has subscribed to events from network devices that are configured to trigger the RIC to provide coordination policies.

[0077] In some embodiments, the RIC provides a coordination strategy based on artificial intelligence inference.

[0078] In some embodiments, the RIC maintains state information and static information.

[0079] In some embodiments, the status information of the terminal device includes: measurements of the terminal device and / or connection information of the terminal device.

[0080] In some embodiments, the static information of the network includes: configuration geographical parameters and physical parameters of the reliability group.

[0081] In some embodiments, the coordination policy includes a setting policy, a selection policy, a resource reservation policy and / or a switching policy of a reliability group.

[0082] Figure 4 FIG. 4 is a flow chart showing an example method 400 implemented at a network device according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 Method 400 is described from the perspective of network device 120 .

[0083] At block 410, the network device 120 provides status information from the network device to the network controller or RIC. At block 420, the network device 120 receives a coordination policy from the network controller. At block 430, the network device 130 processes / performs a process for redundant user plane configuration for the terminal device based on the coordination policy.

[0084] In some embodiments, the network controller or RIC has subscribed to status information from network devices.

[0085] In some embodiments, the network controller or RIC has subscribed to events from network devices that are configured to trigger the network controller to provide coordination policies.

[0086] In some embodiments, the status information is near real-time status information of the network device.

[0087] In some embodiments, the static information of the network includes: configuration of reliability groups, geographical parameters, and physical parameters.

[0088] In some embodiments, the process of the PDU session includes at least one of an establishment process, a resource reservation process, and a switching process.

[0089] In some embodiments, the network device has information of more than one terminal device belonging to the same terminal device group, and the information of the more than one terminal device is reported by the network device to the network controller.

[0090] Figure 5 FIG. 5 is a flow chart showing an example method 500 implemented at a terminal device according to some embodiments of the present disclosure. For the purpose of discussion, reference will be made to Figure 1 The method 500 is described from the perspective of the terminal device 130 .

[0091] At block 510, the terminal device 130 provides status information from the terminal device to a network device, wherein the status information includes measurements of the terminal device.

[0092] At block 520 , the terminal device 130 sends a request for a protocol data unit (PDU) session to a network device to which the terminal device belongs.

[0093] In some embodiments, the status information is near real-time status information of the terminal device.

[0094] In some embodiments, the status information of the terminal device includes: measurements of the terminal device and / or connection information of the terminal device.

[0095] In some embodiments, the terminal device has information of more than one terminal device belonging to the same terminal device group, which is reported to the network device or subscribed by the network device.

[0096] Reference now Figure 6 , which shows a flow chart of a method implemented at the RIC regarding outputting a coordination strategy for reliability groups and diversity / redundancy through an AI algorithm.

[0097] Based on at least one of the status information between network devices in different reliability groups, the status information of terminal devices in the same terminal device group, the static information of the network and the priority factor for diversity / redundancy calculation, the RIC 110 provides the reliability group and diversity / redundancy selection strategy. In some embodiments, the priority factor for diversity / redundancy calculation is an input from OAM, non-real-time RIC or CN.

[0098] In step 610, the RIC 110 obtains status information between network devices in different reliability groups, status information of terminal devices in the same terminal device group, static information of the network, and priority factors for diversity / redundancy calculation.

[0099] In step 620, the AI ​​function in RIC 110 predicts the UE mobility trajectory, cell load and / or channel quality of the terminal device based on the status information of the terminal devices in the same terminal device group, the status information of the network devices and / or the static information of the network. The prediction result is provided to the coordination function.

[0100] At step 630, the coordination function in the RIC 110 derives candidate RGs by diversity / redundancy based on at least one of status information of terminal devices in the same terminal device group, static information of the network, and a priority factor for diversity / redundancy calculation.

[0101] At step 640, the coordination function in the RIC 110 outputs a coordination strategy for reliability groups and diversity / redundancy based on the candidate RGs and the prediction results from the AI ​​function.

[0102] In some embodiments, the status information may include near real-time measurements of terminal devices, connection information of terminal devices, near real-time measurements of network devices, etc.

[0103] In some embodiments, near real-time measurements of network equipment may include cell load, interference, and the like.

[0104] In some embodiments, the connection information of the terminal device may include candidate network device information of different terminal devices.

[0105] In some embodiments, near real-time measurements of terminal devices may include network device beam parameters, channel measurements, etc.

[0106] Figure 7 is a simplified block diagram of a device 700 suitable for implementing embodiments of the present disclosure. The device 700 may be provided to implement a communication device, such as Figure 1 The terminal device 130 or terminal device 135, the network device 120 or network device 125, and the RIC 110 are shown. As shown in the figure, the device 700 includes one or more processors 710 and one or more memories 720 coupled to the processors 710.

[0107] Processor 710 may be of any type suitable for the local technology network and may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. Device 700 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock that synchronizes a main processor.

[0108] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist over the duration of a power outage.

[0109] Computer program 730 includes computer executable instructions executed by associated processor 710. Program 730 may be stored in ROM 720. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 722.

[0110] The embodiment of the present invention can be implemented with the help of program 730, so that the device 700 can execute the following steps: Figures 2 to 6 Any process of the present invention discussed. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0111] In some embodiments, the program 730 may be tangibly embodied in a computer-readable medium, which may be included in the device 700 (such as in the memory 720) or in other storage devices accessible by the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer readable medium 800 in the form of a CD or DVD is shown. The computer readable medium has a program 730 stored thereon.

[0112] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers, or other computing devices, or some combination thereof, as non-limiting examples.

[0113] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions such as those included in a program module that are executed in a device on a target real or virtual processor to perform the above-referenced Figures 2 to 6 The method 600 is described. In general, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or separated between program modules as needed in various embodiments. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0114] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code enables the function / operation specified in the flow chart and / or block diagram to be realized when the processor or controller executes the program code. The program code can be executed completely on the machine, partially on the machine, as an independent software package, partially on the machine, partially on a remote machine, or completely on a remote machine or server.

[0115] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0116] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, device or apparatus, or any suitable combination of the foregoing. More specific examples of computer readable storage media will include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0117] In addition, although operations are described in a particular order, this should not be understood as requiring the specific order shown or to perform these operations in sequence, or to perform all the operations shown, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features peculiar to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0118] Although the disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as example forms of implementing the claims.

Claims

1. A network controller, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the network controller to at least perform: receiving status information from a network device among a plurality of network devices managed by the network controller, the status information comprising: measurements provided by a terminal device to the network device, and measurements specific to the network device; Determining a coordination strategy based on the state information, the coordination strategy indicating a plurality of redundant user paths set by the network device for the terminal device; and The coordination policy is provided to the network device. 2 . The network controller according to claim 1 , further configured to: obtain static information describing configurations of the plurality of network devices, and determine the coordination strategy based on the state information and the static information.

3. The network controller according to claim 1 or 2 is also configured to: provide diversity / redundancy to a non-real-time network intelligent controller, operation management and maintenance OAM, and / or a 5G core network, wherein the diversity / redundancy is calculated based on the status information and / or the static information. 4 . The network controller according to claim 1 , further configured to: receive an event from the network device, wherein the event is configured to trigger the network controller to provide the coordination strategy. 5 .

5. The network controller according to any one of claims 1 to 4, further configured to: determine the coordination strategy by using a machine learning model.

6. The network controller according to any one of claims 1 to 5, wherein the status information is at least one of near real-time status information of the terminal device, near real-time status information of the network device, and near real-time status information of a configuration of a reliability group, wherein the reliability group comprises: Configuration of different redundant user paths for the terminal devices in the same terminal device group.

7. The network controller according to any one of claims 1 to 6, wherein the status information of the terminal device comprises: Information indicating a connection status between the terminal device and at least one of the plurality of network devices.

8. The network controller according to any one of claims 1 to 7, wherein the static information comprises: Configuration of reliability groups, geographical parameters and physical parameters, wherein the reliability groups include: configuration of the different redundant user paths for the terminal devices in the same terminal device group.

9. The network controller according to any one of claims 1 to 8, wherein the static information is provided by at least one network system component selected from the group consisting of operation administration and maintenance (OAM), network management system (NMS), and service management and organization (SMO).

10. The network controller according to any one of claims 1 to 9, wherein the coordination strategy comprises: At least one of a setting policy, a resource reservation policy, and a switching policy.

11. The network controller according to any one of claims 1 to 10, wherein the network controller is any one of a network intelligent controller (RIC), a non-real-time network intelligent controller (Non-RT RIC), or a near-real-time network intelligent controller (Near-RT RIC).

12. A network device comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the network device to at least perform: Providing status information to a network controller that manages a plurality of network devices, the status information comprising: measurements provided by a terminal device to the network device, and measurements specific to the network device; receiving a coordination policy from the network controller, the coordination policy indicating a plurality of redundant user paths set by the network device for the terminal device; and A process of redundant user plane configuration for the terminal device is handled based on the coordination strategy. 13 . The network device according to claim 12 , further configured to provide an event to the network controller to trigger the network controller to provide the coordination strategy.

14. The network device according to claim 12 or 13, wherein the status information is near real-time status information of the network device.

15. The network device according to any one of claims 12 to 14, wherein the network status information comprises: Information on cell load and interference.

16. The network device according to any one of claims 12 to 15, wherein the redundant user plane configuration process comprises: At least one of an establishment procedure, a resource reservation procedure, and a handover procedure.

17. The network device according to any one of claims 12 to 16, wherein the network device has information of more than one terminal device belonging to the same terminal device group, and the information of the more than one terminal device is reported by the network device to the network controller.

18. A terminal device, comprising: at least one processor; as well as At least one memory storing instructions, wherein when the instructions are executed by the at least one processor, the terminal device at least performs: providing status information to a network device, the status information comprising measurements of the terminal device; and A request for a protocol data unit (PDU) session is transmitted to the network device.

19. The terminal device according to claim 18, wherein the status information is near real-time status information of the terminal device.

20. The terminal device according to claim 18 or 19, wherein the status information of the terminal device comprises: Measurements of the terminal device, and / or connection information of the terminal device.

21. The terminal device according to any one of claims 18 to 20, wherein the terminal device has information of more than one terminal device belonging to the same terminal device group, the information being provided to the network device.

22. A method comprising: At a network controller of a network system, receiving status information from a network device, the network controller managing a plurality of network devices, wherein the status information includes: measurements provided to the network device by a terminal device, and measurements specific to the network device; The network controller determines a coordination strategy based on the state information, wherein the coordination strategy indicates a plurality of redundant user paths set by the network device for the terminal device; and The coordination policy is provided by the network controller to the network device.

23. A method comprising: The network device provides status information to a network controller, the network controller managing a plurality of network devices, the status information comprising: measurements provided by a terminal device to the network device, and measurements specific to the network device; At the network device, receiving a coordination policy from the network controller, the coordination policy indicating a plurality of redundant user paths set by the network device for the terminal device; and A process of redundant user plane configuration for the terminal device is handled based on the coordination strategy.

24. A method comprising: providing status information from a terminal device to a network device, the status information comprising measurements of the terminal device; as well as A request for a protocol data unit (PDU) session is sent to the network device, wherein the terminal device belongs to the network device.

25. A non-transitory computer readable medium comprising program instructions for causing an apparatus to perform the method according to claim 22, 23 or 24.

Images