Operator network identification in network sharing

By transmitting the identification of multiple operator networks within the network device, the problem of insufficient operator identification in the network sharing architecture is solved, and the consistency of correct identification and resource scheduling of operator networks in the decomposition architecture is achieved, thereby avoiding errors Statistics and billing.

CN114788392BActive Publication Date: 2024-11-19ALCATEL LUCENT SHANGHAI BELL CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980102886.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-12-13
Publication Date
2024-11-19
Estimated Expiration
2039-12-13

AI Technical Summary

Technical Problem

In network sharing architecture, the lack of appropriate operator network identification leads to inconsistent behavior among operators, leading to incorrect statistics and billing, and it is difficult to correctly identify operator networks in decomposition architecture, affecting the consistency and interoperability of resource sharing sex.

Method used

By transmitting the identification of multiple operator networks between different devices or network entities within the network device, the first network device is allowed to send a first operator network identifier for determining the service terminal contact to the second network device and allows the first network device to send the first operator network identifier to determine the service terminal contact to the second network device and to allow the first network device to send the first operator network identifier to determine the service terminal contact, and to allow the first network device to send the first operator network identifier to determine the service terminal contact to the second network device and to allow the first network device to send the first operator network identifier to determine the service terminal contact, and to allow the first network device to send the first network device to send the first operator network identifier to determine the service terminal contact, and to allow the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to send the first network device to Second, network equipment independently selects the appropriate operator network to provide services, ensuring that business is guided to the correct endpoints and avoids conflicts.

Benefits of technology

In a dual-connection scenario, by transmitting the identification of multiple operator networks, it is possible to distinguish operator networks selected by different network devices in the decomposition architecture, resolve service termination conflicts and avoid incorrect business statistics, and ensure the correct resource scheduling and the accuracy of billing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114788392B_ABST
    Figure CN114788392B_ABST
Patent Text Reader

Abstract

Example embodiments of the present application relate to operator network identification. According to some example embodiments, a first device included in a second network device obtains a first identification of a first operator network for determining a service termination point associated with a terminal device from a first network device. The second network device is configured to provide dual connectivity to the terminal device together with the first network device. The first device determines a second operator network for serving the terminal device through the second network device, and sends information about the first identification of the first operator network and the second identification of the second operator to a second device included in the second network device. Through this solution, in a dual connectivity scenario, in a network device having a decomposed architecture, operator networks selected by different network devices can be distinguished.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present application generally relate to the field of telecommunications, and more particularly to methods, devices, apparatuses, and computer-readable storage media for operator network identification. Background Art

[0002] As communication systems evolve, new technologies are proposed. The next generation of communication systems is expected to support explosive data traffic, greatly increased transmission rates per user, significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To this end, various technologies have been developed.

[0003] Traditionally, each operator provides its own core network as well as its own radio access network (RAN) to provide access to the operator's core network. However, the deployment of the network requires high effort and cost. Therefore, a network sharing architecture is proposed, which allows different operators to share a common network and thus share network resources according to an agreed allocation scheme. The identification of networks for different operators is important in the network sharing architecture. Summary of the invention

[0004] In general, example embodiments of the present application provide a solution for operator network identification.

[0005] In a first aspect, a first device is provided. The first device includes at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to use the at least one processor to cause the first device to obtain, from a first network device, a first identifier of a first operator network for determining a service termination point associated with a terminal device, the first device being included in a second network device, and the second network device being configured to provide dual connectivity to the terminal device together with the first network device; determine a second operator network for serving the terminal device through the second network device; and transmit information about the first identifier of the first operator network and the second identifier of the second operator network to a second device included in the second network device.

[0006] In a second aspect, a second device is provided. A first device includes at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to use the at least one processor to cause the second device to receive information about a first identifier of a first operator network and a second identifier of a second operator network from a first device included in a second network device, the second device being included in the second network device, and the second network device being configured to provide dual connectivity to a terminal device together with the first network device; identify a termination point of a service associated with the terminal device based on the first identifier; and identify a second operator network for providing services to the terminal device through the second network device based on the second identifier.

[0007] In a third aspect, a network device is provided. The network device includes a first network entity configured to: obtain a first identifier of a first operator network for determining a service termination point associated with a terminal device from another network device, wherein the network device is configured to provide dual connectivity to the terminal device together with the other network device, determine a second operator network for serving the terminal device through a second network device, and provide information about a first identifier of the first operator network and a second identifier of the second operator network; and a second network entity communicatively coupled to the first network entity and configured to obtain information about the first identifier and the second identifier from the first network entity.

[0008] In a fourth aspect, a method is provided. The method includes: obtaining, at a first device included in a second network device, a first identifier of a first operator network for determining a service termination point associated with a terminal device from the first network device, and the second network device is configured to provide dual connectivity to the terminal device together with the first network device; determining a second operator network for serving the terminal device through the second network device; and transmitting information about the first identifier of the first operator network and the second identifier of the second operator network to a second device included in the second network device.

[0009] In a fifth aspect, a method is provided. The method comprises: receiving, at a second device and from a first device, information about a first identifier of a first operator network and a second identifier of a second operator network, the first and second devices being included in a second network device, and the second network device being configured to provide dual connectivity for a terminal device together with the first network device; identifying a service termination point associated with the terminal device based on the first identifier; and identifying the second operator network serving the terminal device through the second network device based on the second identifier.

[0010] In a sixth aspect, a first device is provided. The first device includes means for: acquiring a first identifier of a first operator network for determining a service termination point associated with a terminal device from a first network device, the first device being included in a second network device, and the second network device being configured to provide dual connectivity to the terminal device together with the first network device; determining a second operator network for serving the terminal device through the second network device; and transmitting information about the first identifier of the first operator network and the second identifier of the second operator network to a second device included in the second network device.

[0011] In a seventh aspect, a second device is provided. The second device includes means for: receiving information about a first identifier of a first operator network and a second identifier of a second operator network from a first device, the first and second devices being included in the second network device, and the second network device being configured to provide dual connectivity for a terminal device together with the first network device; identifying a service termination point associated with the terminal device based on the first identifier; and identifying the second operator network serving the terminal device through the second network device based on the second identifier.

[0012] In an eighth aspect, a device is provided, which includes the first device of the sixth aspect and the second device of the seventh aspect.

[0013] In a ninth aspect, a computer-readable medium is provided, wherein the computer-readable medium includes program instructions for causing an apparatus to execute a method according to at least any one of the fourth and fifth aspects.

[0014] It should be understood that the abstract is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended 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

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

[0016] Figure 1 An example communication environment is shown in which example embodiments of the present application may be implemented;

[0017] Figure 2 A block diagram of an example network device having a disaggregated architecture is shown;

[0018] Figure 3 The signaling process for operator network identification according to some example embodiments of the present application is shown;

[0019] Figure 4A signaling process for transmitting a context management message according to some example embodiments of the present application is shown;

[0020] Figure 5 A signaling flow for transmitting a context management message according to some further example embodiments of the present application is shown;

[0021] Figure 6 A flowchart showing a method implemented on a first device according to some example embodiments of the present application is shown;

[0022] Figure 7 A flowchart showing a method implemented on a second device according to some other exemplary embodiments of the present application;

[0023] Figure 8 shows a simplified block diagram of an apparatus suitable for implementing an example embodiment of the present application; and

[0024] Fig. 9 A block diagram of an example computer-readable medium according to some example embodiments of the present application is shown.

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

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

[0027] 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 application belongs.

[0028] References in this application to "one embodiment," "an embodiment," "an exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not necessarily every embodiment includes the particular feature, structure, or characteristic. In addition, these terms 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 those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0029] It should be understood that although the terms "first" and "second" 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 example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0030] 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 one" are also intended to include the plural forms unless the context clearly indicates otherwise. It will be further understood that the terms "comprise", "include", "contain", "have", "include" and / or "comprising", when used herein, specify the presence of the features, elements and / or parts, etc., but do not exclude the presence or addition of one or more other features, elements, parts and / or combinations thereof.

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

[0032] (a) implemented in hardware circuits only (e.g. implemented in analog and / or digital circuits only); and

[0033] (b) A combination of hardware circuits and software, such as (as applicable):

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

[0035] (ii) any portion of a hardware processor(s) (including a digital signal processor), software and memory(s) with software that work together to enable a device (e.g. a mobile phone or server) to perform various functions; and

[0036] (c)(one or more) hardware circuits and or processors, such as(one or more) microprocessors or portions of(one or more) microprocessors, that require software (e.g., firmware) for operation, but the software may not be present when it is not required for operation.

[0037] 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 covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, if applicable to the particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0038] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), 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 carried out according to any suitable generations of communication protocols, including but not limited to the first generation (1G), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth generation (4G), 4.5G, the future fifth generation (5G) communication protocol and / or any other currently known or to be developed in the future protocol. The embodiments of the present application can be applied in various communication systems. In view of the rapid development of communication, there will certainly be future types of communication technologies and systems in which the present application can be implemented. The scope of the present application should not be considered to be limited to the above-mentioned system.

[0039] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services therefrom. A network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (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), a relay, a low-power node (e.g., a femto, a pico base station), a non-terrestrial network (NTN) or non-terrestrial network equipment, such as satellite network equipment, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network equipment, etc., depending on the terminology and technology applied.

[0040] 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), user station (SS), portable user station, mobile station (MS) or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (e.g., digital cameras), game terminal devices, music storage and playback devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, computer embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless client devices (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0041] Example environment and working principle

[0042] With the development of telecommunications, support for network sharing between different operators has been proposed. The network sharing architecture should allow multiple participating operators to share one or more common networks and their resources according to an agreed allocation scheme. The shared network includes the Radio Access Network (RAN). The shared resources include radio resources. Network sharing is a way for operators to share the heavy deployment costs of the transport network. In addition to this shared RAN, the operator may or may not have an additional dedicated radio access network.

[0043] RAN sharing can be achieved through two standardized architectures. The first architecture is called Mobile Operator Core Network (MOCN) and consists of different participating operators that connect their core network (CN) infrastructure to a common shared RAN. In this case, each participating operator can run the CN-RAN procedures from its own managed RAN. In the MOCN architecture, the RAN routes the UE's initial access to the shared network to one of the available CN nodes. The supported UE should inform the RAN of the selected core network operator so that the RAN can route correctly. The second architecture option is called Gateway Core Network (GWCN) and it consists of a shared RAN connected to a single shared CN. Therefore, the participating operators will share the CN as well as the RAN.

[0044] Figure 1 An example communication environment 100 for network sharing is shown, in which example embodiments of the present application may be implemented. Figure 1 In the example of , core network 110-1 and core network 110-2 are provided and operated by two different operators (i.e., a first operator and a second operator). The operators can be identified by corresponding identifiers. In one example, different operators are identified by corresponding public land mobile network (PLMN) identifiers. Therefore, as an example, the first operator of core network 110-1 can be identified by the identifier "PLMN ID1", and the second operator of core network 110-2 can be identified by the identifier "PLMN ID2".

[0045] In the network sharing scenario, the RAN is shared by two operators. As shown in the figure, the network device 120-1 as the access node of the RAN is connected to both the core networks 100-1 and 110-2, for example, connected to one or more core network entities via an S1-U interface. Another network device 120-2 is also connected to both the core networks 100-1 and 110-2, for example, connected to one or more core network entities via an S1-U interface. In such an architecture, the two core networks 100-1 and 110-2 can share the radio resources in the network device 120-1 and the network device 120-2.

[0046] In some example embodiments, core network 110-3 also shares network device 120-2. For example, core network 110-3 is also provided and operated by the same second operator of core network 110-2, and can therefore be identified by the identity of the second operator. In some example embodiments, there may be one or more network devices that are not shared by different operators. For example, network device 120-3 is only connected to core network 110-3 of the second operator.

[0047] Here, core networks 110-1, 110-2, and 110-3 are collectively or individually referred to as core networks 110, and network devices 120-1, 120-2, and 120-3 are collectively or individually referred to as network devices 120. Figure 1In the example shown, the network of the first operator (also referred to as the "first operator network") may include a core network 110-1, a network device 120-1, and a network device 120-1. The network of the second operator (also referred to as the "second operator network") may include a core network 110-2, a core network 110-3, and network devices 120-1 to 120-3. Network devices 120-1 and 120-2 (and their access resources in the corresponding RAN) are shared by the first and second operators. In this example, two operators (e.g., identified by PLMN ID1 and PLMN ID2) share radio resource management (RRM) resources and a transport network for the X2 interface. Network device 120-1 may be a 4G eNB, and network device 120-2 may be a 5G gNB. In this case, the two PLMNs share resources in the 4G eNB and the 5G gNB. In this example, the operators do not share a core network, and each PLMN has its own core network, and the eNB / gNB needs to be connected to these networks separately.

[0048] In some example embodiments, one or more of network devices 120 may be implemented in a disaggregated architecture, where different separate logical network entities are configured to handle respective functions. A gNB in ​​NR is an example of such a network device that may be implemented in a disaggregated architecture.

[0049] Figure 2 An example of a network device 120 having a decomposed architecture is shown. As shown, the network device 120 is composed of multiple network entities, including a central unit control plane (CU-CP) 210, one or more central unit user planes (CU-UPs) 220-1, 220-2, ..., 220-N (collectively or individually referred to as CU-UP 220, where N is an integer equal to or greater than one), and one or more distributed units (DUs) 230-1, ..., 230-M (collectively or individually referred to as DU 230, where M is an integer equal to or greater than 1). In an example where the network device 120 is a gNB, the CU-CP 210 may be referred to as a gNB-CU-CP, the CU-UP 220 may be referred to as a gNB-CU-UP, and the DU 230 may be referred to as a gNB-DU.

[0050] In some example embodiments, CU-CP 210 and CU-UP 220 together implement the functionality of a central unit (CU) of network device 120. In some example embodiments, CU-CP 210 is a logical node or entity that hosts the control plane portion of the radio resource control (RRC) and packet data convergence protocol (PDCP) protocols for the CU of network device 120. CU-CP 210 may terminate at an E1 interface connected to CU-UP 220 and an F1-C interface connected to DU 230. In some example embodiments, CU-UP 220 is a logical node or entity that hosts the user plane portion of the PDCP protocol for the CU of network device 120, as well as the user plane portion of the PDCP protocol and the shared device access protocol (SDAP) protocol for the CU of network device 120. CU-UP 220 may terminate at an E1 interface connected to CU-CP 210 and an F1-U interface connected to DU 230. Figure 2 In the example of , control plane signaling may be performed by CU-CP 210 , while user plane traffic is handled by CU-UP 220 .

[0051] In some example embodiments, DU 230 is a logical node or entity that hosts the radio link control (RLC), media access control (MAC), and physical (PHY) layers of network device 120, and whose operation is controlled in part by the CU of network device 120. One DU 230 may support one or more cells. A cell may be supported by only one DU 230. DU 230 may terminate at an F1 interface connected to the CU.

[0052] exist Figure 2 In the example shown, the CU-CP and CU-UP in the network device 120 are provided separately. In another decomposed architecture, the network device 120 may include a CU and one or more DUs 230. The CU-CP and CU-UP act together as a CU. In this example, the CU may be viewed as a logical node for the RRC, SDAP, and / or PDCP protocols of the network device 120 that hosts and controls the operation of one or more DUs 230. The CU may be terminated at an F1 interface connected to the DU 230. It will be appreciated that the network device 120 may be designed to have any other decomposed architecture.

[0053] In environment 100, terminal device 130 can communicate with one or more operator networks through network devices. Terminal device 130 can support dual connectivity (DC), in which terminal device 130 maintains a radio resource control (RRC) connection with a serving cell from a master node (MN), and terminal device 130 can be configured to have a connection to a secondary node (SN) for additional throughput. MN and SN are connected to each other through a backhaul interface, such as an X2-U interface, an X2-C interface, an Xn-U interface, and / or an Xn-C interface. Figure 1 In the example of , terminal device 130 is connected to network device 120-1 and network device 120-2. Network device 120-1 can act as an MN, and network device 120-2 can act as an SN for terminal device 130 in DC.

[0054] Different DC options may be applied to the terminal device 130. One option may include an evolved UMTS terrestrial radio access network (E-UTRAN)-NR DC (EN-DC) mode, in which the MN for the terminal device 130 is an eNB (e.g., network device 120-1 is an eNB) and the SN for the terminal device 130 is an NR gNB (e.g., network device 120-2 is a gNB). The EN-DC mode is a specific example of multi-RAT DC (MR-DC) supported by the terminal device 130. Another DC option may include NR DC, in which the terminal device 130 is connected to an NR gNB acting as a MN and another NR gNB acting as a SN (i.e., network devices 110-1 and 110-2 are both gNBs). In DC, at least the MN is connected to an operator network. In some example embodiments, the SN may also be connected to the operator network.

[0055] It should be understood that the number of devices and networks and their connections are for illustration purposes only and do not imply any limitation. Environment 100 may include any suitable number of devices and networks suitable for implementing embodiments of the present application.

[0056] The communication in the communication environment 100 can be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols of the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G) and fifth generation (5G), as well 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 developed in the future.

[0057] In a communication environment where network sharing is deployed, if one or more network devices are in a disaggregated architecture, there may be some communication scenarios where conflicts and inconsistent behaviors occur due to the lack of appropriate means to correctly identify the operator identity consistently between different logical entities of the network device. Conflicts and inconsistent behaviors are particularly pressing in DCs.

[0058] In the DC scenario, the MN for the terminal device in the DC indicates to the SN the identifier of the operator network used to determine the termination point of the service communication. In this way, the SN can know which operator network the service needs to traverse from the SN. The identifier of the operator network usually matches the core network used in the MN. Therefore, the MN can send a signal to the SN to notify the S1-U termination point pointing to the core network selected and used by the MN.

[0059] On the SN side, the main problem is that currently only one identity of an operator network is allowed to be signaled between different network entities in the decomposed architecture of the SN, for example, signaled over the F1 and E1 interfaces. Therefore, in the case where the SN is a network device shared by different operator networks, the SN is restricted in practice to follow the operator network selected by the MN and then signal the identity of the operator network selected by the MN between its network entities, even though it would be beneficial for the SN to be allowed to select the operator network on its own. This restriction causes problems because in many cases the operator network indicated by the MN should not be used to count traffic at the SN, but only to indicate the termination point to which the SN needs to transmit the traffic. Therefore, when the traffic of the terminal device is marked as belonging to an incorrect operator network by the identity signaled by the operator network, it may result in erroneous statistics and user billing. Likewise, the SN is not free to choose the correct identity of the appropriate operator network and must consider all user traffic as belonging to the operator network initially selected by the MN.

[0060] There are some other issues. For example, if there is a list of equivalent operator networks, then during a terminal device handoff, the SN (e.g., the SN's DU) may be able to select the best cell from any of the equivalent operator networks. However, unless the backhaul of these operator networks (e.g., the core network) is also shared, selecting an equivalent operator network instead of the network selected by the MN will lead to inconsistent resource sharing because the operator networks used for cell selection and resource selection are inconsistent or not closely associated.

[0061] To avoid at least some of the potential issues discussed above, in one possible implementation, the SN is not allowed to perform the selection of an operator network, but instead reuses the identity of the same operator network selected by the MN to ensure that traffic is directed to the correct termination point in dual connectivity. With this implementation, in the case of a decomposed architecture for SN gNBs, the gNB-CU-CP always reuses the PLMN ID provided by the MN when establishing UE / bearer contexts via F1 (towards gNB-DU) and via E1 (towards gNB-CU-UP). However, this is undesirable because it artificially imposes restrictions at the SN to prohibit the SN from freely selecting an identity corresponding to a suitable operator, and also forces the SN to consider all user traffic as belonging to the PLMN initially selected by the MN, as mentioned above.

[0062] In summary, the lack of proper operator network identification leads to workarounds and even violations of network sharing in some scenarios. In addition, interoperability issues may occur in inter-operator scenarios due to lack of consistency in behavior and incorrect accounting and billing attributed to the wrong operator network.

[0063] According to some example embodiments of the present application, an improved solution for operator network identification is provided. In this solution, multiple identifications of operator networks can be transmitted between different devices or network entities within a network device. Specifically, a first network device and a second network device are used to provide dual connections to a terminal device, and the first network device sends a first identification of a first operator network for determining a service termination point associated with the terminal device to the second network device. The first device or network entity of the second network device can determine a second operator network for serving the terminal device through the second network device. The first device or network entity of the second network device then transmits the first identification of the first operator network obtained from the first network device and the second identification of the second operator network determined by the second network device to the second device or network entity of the second network device.

[0064] Through this solution, by transmitting the identities of multiple operator networks, the operator networks selected by different network devices can be distinguished within the network device using the decomposed architecture in the DC scenario. When the network device acts as an SN in dual connectivity, it can guide the service to the correct termination point (such as X2-U or S1-U) while maintaining autonomy to select and identify the appropriate operator network for resource scheduling, thereby resolving conflicts with service terminations and avoiding erroneous service statistics.

[0065] The exemplary embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be understood that although some exemplary embodiments of the present application are described below in a network sharing architecture, the present application can also be implemented in other network architectures, such as those without network sharing.

[0066] Example signaling flow

[0067] Reference now Figure 3 , which shows a signaling flow 300 for operator network identification according to some example embodiments of the present application. For the purpose of discussion, reference will be made to Figure 1 300. The signaling flow 300 may involve a network entity 301 and a network entity 302, which are included in a network device having a decomposed architecture, such as Figure 1 In some example embodiments, the signaling flow 300 may also involve another network device, such as Figure 1 and a terminal device, such as terminal device 130. It should be understood that signaling flow 300 may also be implemented in any other communication environment.

[0068] The network device 120-2 with a decomposed architecture is configured to provide DC to the terminal device 130 together with the network device 120-1. The network device 120-1 may be a network device with or without a decomposed architecture. For example, the network device 120-2 may be a gNB, and the network device 120-1 may be an eNB or a gNB. Sometimes, for the purpose of discussion, the network device 120-1 may be referred to as a first network device, and the network device 120-2 may be referred to as a second network device. The terminal device 130 may be any terminal device (or UE) that supports the DC communication mode. The DC provided by the network devices 120-1 and 120-2 may be any applicable DC.

[0069] The network entity 301 and the network entity 302 included in the network device 120-2 may be logical nodes or entities within the network device 120-2, which are communicatively coupled to each other and can send signals between them to notify at least the identity of the operator network. The network entity 301 herein may sometimes be referred to as a first network entity, and the network entity 302 herein may sometimes be referred to as a second network entity. In some example embodiments, the network entity 302 may communicate with the network entity 301 through an interface and be controlled by the network entity 301, and the interface is, for example, an interface defined by 3GPP (e.g., an E1 or F1 interface).

[0070] In the example where the network device 120-2 is a gNB, the network entities 301, 302 may be as follows Figure 2 1 . The network entities 301 and 302 may be different types of logical entities of the network device 120-2 according to different signaling scenarios. For example, in some example embodiments, the network entity 301 may be a CU-CP 210, and the network entity 302 may be a CU-UP 220. In some example embodiments, the network entity 301 may be a CU (i.e., a combination of a CU-CP 210 and a CU-UP 220), and the network entity 302 may be a DU 230. Some specific example signaling scenarios will be further discussed below.

[0071] In the signaling flow 300, a network entity 301 included in the network device 120-2 obtains 305 a first identification of a first operator network for determining a termination point of a service associated with the terminal device 130. In the case where the network devices 120-1, 120-2 are to provide DC to the terminal device 130, the network device 120-1 may be an MN responsible for selecting an operator network for service communications with the terminal device 130, including backhaul services and user service communications. Accordingly, the network device 120-2 may be an SN capable of assisting in service communications for the terminal device 130. In some example embodiments, the network device 120-1 may communicate with the network device 120-2 via a backhaul interface (e.g., an X2-U interface, an X2-C interface, an Xn-U interface, and / or an Xn-C interface).

[0072] In some example embodiments, the first operator network selected by the network device 120-1 may be associated with a specific operator (referred to as a "first operator"), which can be identified by an identifier (i.e., a first identifier). The first operator network may include a core network and a corresponding RAN, which includes one or more network access nodes (including the network device 120-1) to provide radio access. The first operator network selected by the network device 120-1 to act as a MN may match the core network used in the network device 120-1. The first identifier is used to indicate to the network device 120-2 which operator network the service associated with the terminal device 130 needs to traverse from the network device 120-2. The network device 120-2 can use the first identifier to select the correct address (e.g., the correct Internet Protocol (IP) address) to the first operator. Therefore, the service associated with the terminal device 130 can be directed to the correct termination point (e.g., through the X2-U / Xn-U interface, the X2-C / Xn-C interface and / or the S1-U interface). Therefore, the first operator network can be referred to as an operator network associated with the termination point of the backhaul interface in the DC for the terminal device 130 (for example, an operator network associated with the S1-U termination point), and the first identifier can be referred to as a termination point identifier.

[0073] In some example embodiments, the first operator network may be a PLMN and the first identifier may be a PLMN identifier. In some examples, the PLMN identifier may be derived based on a combination of a mobile country code (MCC) and a mobile network code (MNC). It should be understood that other types of applicable operator networks may also be possible. In some example embodiments, network device 120-1 may transmit 310 (which is then obtained by network entity 301) the first identifier or information for deriving the first identifier to network device 120-1.

[0074] As a specific example, the network device 120-1 as an MN may serve the terminal device 130 in the first operator network, and the core network of the first operator network may maintain the context of the terminal device 130. If the network device 120-1 decides to add the network device 120-2 as an SN for the terminal device 130, the network device 120-1 may trigger an SN add request to the network device 120-2, for example, via an X2-C / X2-U interface between the two network devices.

[0075] In an example embodiment of the present application, rather than forcing the network entity 301 of the network device 120-2 to always reuse the first identification selected by the network device 120-1, the entity is allowed to freely select an operator network device for resource scheduling through the network device 120-2 without having to worry about conflicts and inconsistencies in the operator network identification within the network device 120-2. The network device 120-2 can be connected to multiple operator networks, and the radio resources of the network device 120-2 are shared by these operator networks. In this case, the network device 120-2 can select some operator networks to serve the terminal device 130, for example, to provide access resources for communicating with the terminal device 130 through the network device 120-2. Therefore, in the signaling flow 300, the network entity 301 determines 315 a second operator network for serving the terminal device 130 through the network device 120-2.

[0076] In some example embodiments, the second operator network selected by network device 120-1 may be associated with a particular operator (referred to as the "second operator"), which may be identified by an identifier (i.e., a second identifier). The second operator network may include a core network and a corresponding RAN, which includes one or more network access nodes (including network device 120-2) to provide radio access. In some example embodiments, network device 120-2 is shared by at least the first and second operators (if the two operators are different). Therefore, radio resources of network device 120-2 may be scheduled for communications associated with the two operators, and network device 120-2 may need to correctly distinguish between the two operators and their operator networks, for example, by their corresponding identifiers.

[0077] When the second operator network is selected for resource scheduling for the terminal device 130 by the network device 120-2, the second operator network may be referred to as a serving operator network, which provides services for the terminal device 130 in the RAN of the network device 120-2, because the resources of the second operator network are scheduled for communication between the network device 120-2 and the terminal device 130. It should be noted that all terminations for services for the terminal device 130 are still addressed to the first operator network selected by the network device 120-1 acting as the MN.

[0078] In some example embodiments, the second operator network may be a PLMN, and the second identifier may be a PLMN identifier. In some examples, the PLMN identifier may be derived based on a combination of an MCC and an MNC. It should be understood that other types of applicable operator networks may also be possible.

[0079] In some example embodiments, the network entity 301 may select the second operator network to be associated with the same operator as the first operator of the first operator network selected by the network device 120-1, or an operator different from the first operator. The network entity 301 may follow various criteria to select the second operator network as a network different from the first operator network. In some example embodiments, the network entity 301 may determine whether a cell assigned to the first operator network is available for the terminal device 130. The cell corresponds to a coverage area served by a network device shared by the first operator network. If no cell assigned to the first operator network is available, it may mean that the terminal device 130 is moving to a different area without the service of the first operator network, or all cells assigned to the first operator network are overloaded. In this case, the network entity 301 may select or reselect the second operator network for the terminal device 130.

[0080] In some example embodiments, the second operator network may be selected from a list of equivalent operator networks for the first operator network. The network entity 301 may obtain an identifier of the list of equivalent operator networks. The list may include the first operator network and one or more other operator networks equivalent to the first operator network. As used herein, an equivalent operator network of the first operator network may be considered to be equivalent to the first operator network in terms of operator network selection or reselection, cell selection or reselection, and handover. The list of equivalent operator networks may be defined, for example, by the first operator. In some example embodiments, the list of equivalent operator networks may include a list of handover restrictions. The network entity 301 may be able to select one of the equivalent operator networks in the list as the second operator network, for example, when no suitable cell of the first operator network is available.

[0081] Return to reference Figure 3 , in the case where the second operator network is determined, the network entity 301 transmits 320 information about a first identification of the first operator network and a second identification of the second operator network to the network entity 302. The network entity 302 receives 325 information about the first and second entities from the network entity 301. The network entity 302 can thus identify 330 a service termination point associated with the terminal device 130 (i.e., a termination point in the first operator network) based on the first identification, and identify 335 a second operator network for serving the terminal device 130 via the network device 120-2 based on the second identification.

[0082] In an example embodiment of the present application, a first operator network selected by network device 120-1 for determining a service termination point associated with terminal device 130 and a second operator network selected by network device 120-2 for serving terminal device 130 through network device 120-2 may be distinguished.

[0083] In some example embodiments, if the second operator network selected by network device 120-2 for serving terminal device 130 is different from the first operator network device selected by network device 120-1 for determining the service termination point, that is, the second identifier is different from the first identifier, then network entity 301 can transmit the first and second identifiers to network entity 302 in separate information elements (IEs). That is, the first and second identifiers have respective IEs for transmission. In some example embodiments, if the second identifier is the same as the first identifier, it means that network device 120-2 still decides to reuse the first operator network to serve terminal device 130, and one of the first and second identifiers can be sent, for example, in its corresponding IE. When network entity 302 receives such information, it can determine that the first identifier and the second identifier are the same.

[0084] In some example embodiments, when the second operator network is different from the first operator network, by signaling the second identifier of the second operator network to the network entity 302 responsible for managing the context associated with the terminal device 130, the network entity 302 can therefore correctly identify the user service and corresponding billing of the terminal device 130 as belonging to the correct second operator network based on the second identifier. In addition, all services associated with the terminal device 130 can still be directed to the correct termination point selected by the network device 120-1. In addition, in some example embodiments of the present application, the operator network identifier can also be further evidence of a possible roaming event, in which the termination point will need to be updated without affecting the operator network to which the service is marked (the second operator in some of the above examples).

[0085] Example trigger for sending identity

[0086] There are various triggers for transmitting the information about the first and second identities from the network entity 301 to the network entity 302. In some example embodiments, the network entity 302 may be a logical unit of the network device 120-2 configured to manage (e.g., establish or modify) a context associated with the terminal device 130. For example, the network entity 302 may be a CU-UP for managing a bearer context associated with the terminal device 130 or a DU for managing a UE context associated with the terminal device 130. In this case, if the network entity 301 determines to establish or modify a context associated with the terminal device 130, it may transmit the information about the first and second identities to the network entity 302 in a context management message. In some example embodiments, the information about the first and second identities may be transmitted in a context establishment request (e.g., a bearer context establishment request or a UE context establishment request) or in a context modification request (e.g., a bearer context modification request or a UE context modification request).

[0087] In some example embodiments, when a context modification request (e.g., a bearer context modification request or a UE context modification request) receives first and second identifiers of first and second operator networks, network entity 302 may be able to check the compatibility of the operator networks. Specifically, network entity 302 may determine whether the second operator network is compatible with the first operator network. If the second operator network is compatible with the first operator network, network entity 302 may modify the context (i.e., bearer or UE context) associated with the second operator network for the terminal device. Network entity 302 may send a context modification response to network entity 301 to indicate that the context has been modified. If the second operator network is not compatible with the first operator network, network entity 302 may send a context modification response to network entity 301 to reject the context modification request.

[0088] In some example embodiments, if the identifier of the operator network used to determine the termination point changes, for example, from the third identifier of the third operator network to the first identifier of the first operator network, the network entity 301 may transmit the IE corresponding to the first identifier to the network entity 302 in the context modification request. Therefore, the network entity 302 may determine that the identifier of the operator network used to serve the terminal device 130 through the network device 120-2 remains unchanged (for example, still the second identifier of the second operator network). The network entity 302 may still check the compatibility of the two operator networks.

[0089] Similarly, if the identifier of the operator network used to serve the terminal device 130 through the network device 120-2 is changed from the fourth identifier of the fourth operator network to the first identifier of the first operator network, the network entity 301 can transmit the IE corresponding to the first identifier to the network entity 302 in the context modification request. Therefore, the network entity 302 can determine that the identifier of the operator network used to determine the termination point remains unchanged (for example, it is still the first identifier of the first operator network). The network entity 302 can still check the compatibility of the two operator networks.

[0090] In the example where the network entity 301 is the CU-CP 210 of the network device 120-2, it may be configured to send a bearer context establishment request or a bearer modification request including the first and second identifiers to the network entity 302, which may be the CU-UP 220 of the network device 120-2. The bearer context establishment request or the bearer modification request may be sent from the CU-CP 210 to the CU-UP 220 via an interface (e.g., an E1 interface) connected therebetween.

[0091] Since the traditional format of the bearer context establishment request can only be used to indicate one identifier of an operator network, and the identifier of the operator network is not transmitted in the bearer modification request, in some example embodiments, in order to transmit information about the first and second identifiers, the format of the bearer context establishment request or the bearer modification request can be extended to include two IEs for carrying the first and second identifiers. Therefore, the E1 application protocol can be updated to specify the extended format of the bearer context establishment request or the bearer modification request.

[0092] In one example, the Bearer Context Establishment Request specified in Section 9.2.2.1 of 3GPP TS 38.463 (which is a specification related to the E1 application protocol) may be updated to include an IE for carrying an operator network identification as provided in Table 1 below.

[0093] Table 1 Example specification for IE carrying identification

[0094]

[0095] It should be noted that PLMN is an example operator network, PLMN identity is an example identity of an operator network in Table 1, and in addition to the IEs listed above, the bearer context establishment request may contain one or more other IEs for carrying other information. In this example, the IE "Serving PLMN" is used to carry the second identity of the second operator network, and the IE "Termination Point PLMN ID" is used to carry the first identity of the first operator network. If the presence of the IE "Termination Point PLMN ID" in the bearer context establishment request is optional (indicated as "O"), it means that if the second identity of the second operator network (i.e., the identity of the serving PLMN) is the same as the first identity of the first operator network (i.e., the identity of the termination point PLMN ID), the IE "Termination Point PLMN ID" may not be specifically included in the request, and the recipient of the request may use the identity of the serving PLMN as the identity of the termination point PLMN. The presence of the IE "Serving PLMN" is usually necessary (marked as "M" to indicate mandatory) in order to establish a bearer context at the CU-UP. IE "Termination Point PLMN ID" is an additional IE to be added to the bearer context establishment request. It should be understood that the name of this IE is just an example and other names may also be possible.

[0096] In one example, the bearer context modification request specified in 3GPP TS 38.463 Section 9.2.2.4 may also be updated to include an IE for carrying the operator network identification as provided in Table 2 below.

[0097] Table 2 Example specification for IE carrying identifier

[0098]

[0099] It should be noted that PLMN is an example operator network, the PLMN identifier is an example identifier of the operator network in Table 2, and in addition to the IEs listed above, the bearer context modification request may contain one or more other IEs for carrying other information. In this example, the presence of IE "Serving PLMN" and IE "Termination Point PLMN ID" in the bearer context modification request is optional (indicated as "O"). If the CU-CP 210 determines to change the serving PLMN for the terminal device 130 to a new PLMN, for example, when the terminal device switches from a cell to a cell of an equivalent operator network across a cell, the IE "Serving PLMN" may be included. If the network device 120-1 acting as an MN needs to update the termination point, for example, in response to one or more roaming events, the IE "Termination Point PLMN ID" may be included. The IE "Serving PLMN" and IE "Termination Point PLMN ID" are additional IEs to be added to the bearer context modification request.

[0100] In an example where the network entity 301 is a CU (a combination of the CU-CP 210 and the CU-UP 220) of the network device 120-2, it may be configured to send a UE context establishment request or a UE modification request including the first and second identities to the network entity 302, which may be the DU 230 of the network device 120-2. The UE context establishment request or the UE modification request may be sent from the CU via an interface (e.g., an F1 interface) connected therebetween.

[0101] Since the traditional format of the UE context establishment request can only be used to indicate one identifier of an operator network, and the identifier of the operator network is not transmitted in the UE context modification request, in some example embodiments, in order to transmit information about the first and second identifiers, the format of the UE context establishment request or the UE context modification request can be extended to include two IEs for carrying the first and second identifiers. Therefore, the F1 application protocol can be updated to specify the extended format of the UE context establishment request or the UE modification request.

[0102] In one example, the UE context establishment request specified in Section 9.2.2.1 of 3GPP TS 38.473 (which is a specification related to the F1 application protocol) may be updated to include an IE for carrying the operator network identity as provided in Table 3 below.

[0103] Table 3 Example specification for IE carrying identifier

[0104]

[0105] It should be noted that PLMN is an example operator network, PLMN identity is an example identity of an operator network in Table 3, and in addition to the IEs listed above, the UE context establishment request may contain one or more other IEs for carrying other information. In this example, the presence of IE "Serving PLMN" and IE "Termination Point PLMN ID" in the UE context establishment request is optional (indicated as "O"). If the CU-CP 210 determines to change the serving PLMN for the terminal device 130 to a new PLMN, for example, when the terminal device switches from a cell to an equivalent operator network across a cell, the IE "Serving PLMN" may be included. If the network device 120-1 acting as an MN needs to update the termination point, for example, in response to one or more roaming events, the IE "Termination Point PLMN ID" may be included. The IE "Termination Point PLMN ID" is an additional IE to be added to the UE context establishment request. In one example, the UE context modification request specified in Section 9.2.2.7 of 3GPP TS 38.473 may also be updated to include an IE for carrying an operator network identity as provided in Table 4 below.

[0106] Table 4 Example specification for IE carrying identifier

[0107]

[0108] It should be noted that PLMN is an example operator network, and the PLMN identifier is an example identifier of the operator network in Table 4. In addition to the IEs listed above, the UE context modification request may contain one or more other IEs for carrying other information. In this example, the presence of IE "Serving PLMN" and IE "Termination Point PLMN ID" in the UE context modification request is optional (indicated as "O"), just like in the UE context establishment request. If the network device 120-1 acting as an MN needs to update the termination point, for example, in response to one or more roaming events, the IE "Termination Point PLMN ID" may be included. The IE "Serving PLMN" and IE "Termination Point PLMN ID" are additional IEs to be added to the UE context modification request.

[0109] It should be understood that some example updates to the bearer / UE context management message are described above. In other example embodiments, the bearer / UE context management message may be updated in other ways to indicate multiple identities of the operator network. The scope of the present application is not limited in this respect.

[0110] The context management message may be transmitted from the network entity 301 (which may be the CU-CP 210 or the CU) to the network entity 302 (which may be the CU-UP 220 or the DU 230) in various possible processes in the network device 120-2 or the network devices 120-1, 120-2 and possibly the terminal device 130 and the network elements in the core network. Some example processes include a process of adding a secondary gNB (SgNB) in the EN-DC in which a UE context establishment message is transmitted, a bearer context establishment process in which a bearer context establishment request and a bearer context modification request are sent, and some processes related to UE handover in which a UE / bearer context modification request is sent. For a better understanding of the transmission of these context management messages, refer to Figure 4-5 Some example processes of message transmission are shown.

[0111] Figure 4 A signaling flow 400 for transmitting UE context management messages according to some example embodiments of the present application is shown. The signaling flow 400 may involve network device 120-1 and network device 120-2 (more specifically, CU 402 is a combination of CU-CP210 and CU-UP 220 and DU 230). The signaling flow 400 is related to the SgNB addition process. It is assumed that network device 120-1 is an eNB that acts as an MN in the DC of terminal device 130, sometimes also referred to as a MeNB, and network device 120-2 is a gNB. In this example, the CU can be considered as a network entity 301 in network device 120-2, and the DU 230 can be considered as a network entity 302 in network device 120-2.

[0112] Specifically, network device 120-1, which is the MN of terminal device 130, determines to add network device 120-2 as the SN of terminal device 130. Therefore, network device 120-1 sends 405 an SgNB add request to CU 402. In some example embodiments, the SgNB add request may carry a source cell group configuration (expressed as "CG-ConfigInfo").

[0113] After receiving the SgNB add request message from network device 120-1, CU 402 sends 410 a UE context establishment request message to DU 230 to establish a UE context. In some example embodiments, the UE context establishment request message may include a first identifier (e.g., PLMN ID1) of a first operator network selected by network device 120-1 for determining a termination point for a service associated with terminal device 130, and a second identifier (e.g., PLMN ID2) of a second operator network selected by CU 402 for providing services to terminal device 130 through network device 120-2. In some example embodiments of the auxiliary node change, the UE context establishment request message may include a source cell group configuration to allow DU 230 to perform incremental configuration.

[0114] DU 230 responds 415 to CU 402 with a UE Context Setup Response message. Upon receiving the UE Context Setup Request message, CU 402 responds 420 to network device 120-1 with an SgNB Add Request Confirm message. In some example embodiments, the SgNB Add Request Confirm message may carry a source cell group configuration.

[0115] It should be understood that the SgNB addition process may include further signaling between the network device 120-1, network entities within the network device 120-1 and possibly the terminal device 130 and one or more network elements in the core network. For the sake of brevity, such signaling is not shown here.

[0116] Figure 5 A signaling flow 500 for transmitting bearer context management messages according to some example embodiments of the present application is shown. The signaling flow 500 may involve network entities within the network device 120-2, including the CU-CP 210, the CU-UP 220, and the DU 230. The signaling flow 500 is related to the process of establishing a bearer context in the CU-UP 220. In this example, it is assumed that the network device 120-2 is a gNB. The CU-CP 210 can be considered as the network entity 301 in the network device 120-2, and the CU-UP 220 can be considered as the network entity 302 in the network device 120-2.

[0117] Specifically, a bearer context establishment is triggered 505 in CU-CP 210 210 (e.g., after an SgNB add request message from network device 120-1). CU-CP 210 sends 510 a bearer context establishment request message to CU-UP 220 to establish a bearer context in CU-UP 220. In some example embodiments, the bearer context establishment request message may include a first identifier (e.g., PLMN ID1) of a first operator network selected by network device 120-1 for determining a termination point for a service associated with terminal device 130, and a second identifier (e.g., PLMN ID1) of a second operator network selected by CU-CP 210 for providing service to terminal device 130 via network device 120-2.

[0118] The CU-UP 220 responds 515 to the CU-CP 210 with a bearer context setup response message. The F1 UE context setup procedure 520 is performed between the CU-CP 210 and the DU 230 to establish one or more bearers in the DU 230.

[0119] CU-CP 210 sends 525 a bearer context modification request message to CU-UP 220. In some example embodiments, the bearer context modification request message may include a first identifier (e.g., PLMN ID1) of a first operator network selected by network device 120-1 for determining a termination point for a service associated with terminal device 130, and a second identifier (e.g., PLMN ID1) of a second operator network selected by CU-CP 210 for providing services to terminal device 130 via network device 120-2. CU-UP 220 responds 530 to CU-CP 210 with a bearer context modification response message.

[0120] In some example embodiments, uplink user data from terminal device 130 may be sent 535 from DU 230 to CU-UP 220 , and downlink user data for terminal device 130 may be sent 540 from CU-UP 220 to DU 230 .

[0121] It should be understood that the above process shown is provided for illustration purposes only and does not imply any limitation on the scope of the present invention. The first and second identities of the first and second operator networks may be notified from a network entity to another network entity within the network device 120-2 in various other processes.

[0122] Example methods implemented at corresponding devices

[0123] Figure 6A flowchart of an example method 600 implemented on a first device according to some example embodiments of the present application is shown. For discussion purposes, reference will be made to Figures 1 to 3 The method 600 is described from the perspective of the network entity 301 (ie, the first device) included in the network apparatus 120 - 2 .

[0124] At block 610, the network entity 301 obtains a first identifier of a first operator network from the network device 120-1 for determining a termination point of a service associated with the terminal device 130. The network device 120-2 and the network device 120-1 are configured to provide a DC to the terminal device 130. The network device 120-1 may be the one responsible for selecting the termination point and may be the MN in the DC. The network device 120-2 may be a device that assists service communications of the terminal device 130 and may be the SN in the DC.

[0125] At block 620, the network entity 301 determines a second operator network for serving the terminal device 130 through the network device 120-2. In an example embodiment of the present application, as described above, the network entity 301 in the network device 120-2 is allowed to freely select an operator network for serving the terminal device 130. In some example embodiments, the second operator network may be the same operator network as the first operator network. In some example embodiments, the second operator network may be selected, for example, from a list of equivalent operator networks for the first operator network. In some example embodiments, the network entity 301 may determine whether a cell allocated to the first operator network is available for the terminal device 130. In the event that a cell is not available, the network entity 301 may select a second operator network equivalent to the first operator network, for example, when a suitable cell allocated to the second operator is available.

[0126] At block 630, the network entity 301 transmits information about the first identifier of the first operator network and the second identifier of the second operator network to the network entity 302 in the network device 120-2. In this way, the network entity 302 can distinguish between the two operator networks, and thus can correctly identify the service termination point associated with the terminal device 130, and the operator network that provides services to the terminal device 130 through the network device 120-2. Therefore, the services associated with the terminal device 130 can be correctly directed to the termination point, and the network entity 302 can also perform correct service statistics and billing for the terminal device 130 for the services provided by the second operator network.

[0127] In some example embodiments, information about the first and second identifiers may be transmitted in separate IEs, particularly if the second identifier is different from the first identifier. In some example embodiments, information about the first and second identifiers may be transmitted in a context establishment request or a context modification request. For example, if network entity 301 is CU-CP 210 of network device 120-2 and network entity 302 is CU-UP 220 of network device 120-2, network entity 301 may send a bearer context establishment request or a bearer context modification request containing information about the first and second identifiers to network entity 302 based on an actual event that triggers the transmission of the corresponding request.

[0128] As another example, if network entity 301 is the CU of network device 120-2 and network entity 302 is DU 230 of network device 120-2, network entity 301 may send a UE context establishment request or a UE context modification request including information about the first and second identifiers to network entity 302 based on an actual event that triggers transmission of the corresponding request.

[0129] Figure 7 A flowchart of an example method 700 implemented at a second device according to some example embodiments of the present application is shown. For discussion purposes, reference will be made to Figure 1-3 The method 700 is described from the perspective of the network entity 302 (ie, the second device) included in the network device 120-2.

[0130] At block 710, network entity 302 receives information about a first identifier of a first operator network and a second identifier of a second operator network from network entity 301 included in network device 120-2. Network device 120-2 and other network devices, such as network device 120-1, are configured to provide DC to terminal device 130. In some example embodiments, the first identifier and the second identifier may be included in separate IEs transmitted from network entity 301, in particular if the second identifier is different from the first identifier. In some example embodiments, the information about the first and second identifiers may be sent in a context establishment request or a context modification request.

[0131] The network entity 302 identifies a service termination point associated with the terminal device 130 based on the first identification at block 720 , and identifies a second operator network for serving the terminal device 130 through the network device 120 based on the second identification at block 730 .

[0132] In some example embodiments, if the information about the first and second identifiers is included in the context modification request, and the second identifier is different from the first identifier, the network entity 302 may check the compatibility of the operator networks identified by the two identifiers to decide whether to accept or reject the context modification request. Specifically, the network entity 302 may determine whether the second operator network is compatible with the first operator network. If the second operator network is compatible with the first operator network, the network entity 302 may modify the context associated with the second operator network for the terminal device 130. If the second operator network is not compatible with the first operator network, the network entity 302 may send a context modification response to the network entity 301 to reject the context modification request.

[0133] Example Device

[0134] In some example embodiments, a first device (e.g., network entity 301) capable of performing any of method 600 may include means for performing the corresponding operations of method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module. The first device may be implemented as network entity 301 or included in network entity 301.

[0135] In some example embodiments, the first device includes a device for: obtaining a first identifier of a first operator network for determining a service termination point associated with a terminal device from a first network device (e.g., network device 120-1), the first device being included in a second network device (e.g., network device 120-2), and the second network device being configured to provide dual connectivity to the terminal device together with the first network device; determining a second operator network for serving the terminal device through the second network device; and transmitting information about the first identifier of the first operator network and the second identifier of the second operator network to a second device included in the second network device (e.g., a device implemented as or included in the network entity 302).

[0136] In some example embodiments, the apparatus for transmitting the information includes an apparatus for: determining whether the second identifier is different from the first identifier; and transmitting the first identifier and the second identifier as separate information elements to the second device based on determining that the second identifier is different from the first identifier.

[0137] In some example embodiments, the means for transmitting the information comprises: means for transmitting the information about the first and second identifiers to the second device in a context establishment request; or means for transmitting the information about the first and second identifiers to the second device in a context modification request.

[0138] In some example embodiments, the means for determining the second operator network includes means for: determining whether a cell allocated to the first operator network is available to the terminal device; and based on determining that the cell is unavailable, selecting a second operator network equivalent to the first operator network.

[0139] In some example embodiments, the first device comprises a central unit of the second network device, and the second device comprises a distributed unit of the second network device.In some example embodiments, the first device comprises a central unit control plane entity of the second network device, and the second device comprises a central unit user plane entity of the second network device.

[0140] In some example embodiments, the first device further comprises means for performing other operations in some example embodiments of method 600. In some example embodiments, the apparatus comprises at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to cause the first apparatus to perform operations with the at least one processor.

[0141] In some example embodiments, a second device (e.g., network entity 302) capable of performing any of method 700 may include means for performing the corresponding operations of method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuit or a software module. The second device may be implemented as network entity 302 or included in network entity 302.

[0142] In some example embodiments, the second device includes a device for: receiving information about a first identifier of a first operator network and a second identifier of a second operator network from a first device (e.g., a device implemented as network entity 301 or included in network entity 301), the first and second devices being included in the second network device, and the second network device being configured to provide dual connectivity to the terminal device together with the first network device; identifying a service termination point associated with the terminal device based on the first identifier; and identifying a second operator network for providing services to the terminal device through the second network device based on the second identifier.

[0143] In some example embodiments, means for receiving information comprises means for receiving a first identification and a second identification from a first device in separate information elements, the first identification being different from the second identification.

[0144] In some example embodiments, the means for receiving information comprises: means for receiving information about the first and second identifiers in a context establishment request from the first device; or means for receiving information about the first and second identifiers in a context modification request from the first device.

[0145] In some example embodiments, wherein information about the first and second identifiers is included in a context modification request, the second device further includes means for: determining whether the second operator network is compatible with the first operator network based on a determination that the second identifier is different from the first identifier; modifying the context associated with the second operator network for the terminal device based on a determination that the second operator network is compatible with the first operator network; and sending a context modification response to the first device to reject the context modification request based on a determination that the second operator network is incompatible with the first operator network.

[0146] In some example embodiments, the first device comprises a central unit of the second network device, and the second device comprises a distributed unit of the second network device.In some example embodiments, the first device comprises a central unit control plane entity of the second network device, and the second device comprises a central unit user plane entity of the second network device.

[0147] In some example embodiments, the second device further comprises means for performing other operations in some example embodiments of method 700. In some example embodiments, the apparatus comprises at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to cause the second device to perform operations using the at least one processor.

[0148] Example devices and computer-readable media

[0149] Figure 8 800 is a simplified block diagram of a device suitable for implementing an example embodiment of the present application. The device 800 may be used to implement a communication device, such as Figure 1 The network device 120 or terminal device 130 shown, or Figure 2 The network entity 301 or the network entity 302 is shown. As shown in the figure, the device 800 includes one or more processors 810, one or more memories 820 coupled to the processors 810, and one or more communication modules 840 coupled to the processors 810.

[0150] The communication module 840 is used for two-way communication. The communication module 840 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required to communicate with other network elements. In some example embodiments, the communication module 840 may include at least one antenna.

[0151] Processor 810 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of 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. Device 800 may have multiple processors, such as application specific integrated circuit chips that are time-controlled by a clock that is synchronized with a main processor.

[0152] The memory 820 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) 824, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), optical disk, laser disk, and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 822 and other volatile memories that will not persist during a power outage.

[0153] The computer program 830 includes computer executable instructions that are executed by the associated processor 810. The program 830 may be stored in a memory such as ROM 824. The processor 810 may perform any suitable actions and processes by loading the program 830 into the RAM 822.

[0154] The exemplary embodiment of the present application can be implemented by the program 830 so that the device 800 can execute the reference Figure 3-7 Any process disclosed in the discussion. The exemplary embodiments of the present application may also be implemented by hardware or by a combination of software and hardware.

[0155] In some example embodiments, the program 830 may be tangibly embodied in a computer-readable medium, which may be contained in the device 800 (such as in the memory 820) or in other storage devices accessible to the device 800. The device 800 may load the program 830 from the computer-readable medium to the RAM 822 for execution. The computer-readable medium may include any type of tangible non-volatile storage, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Fig. 9 An example of a computer readable medium 900 in the form of a CD or DVD is shown. The computer readable medium has a program 830 stored thereon.

[0156] Typically, various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Certain aspects can be implemented in hardware, while other aspects can be implemented in firmware or software, which can be performed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present application 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 can be implemented as non-limiting examples, hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combinations thereof.

[0157] The present application 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 instructions contained in program modules, which are executed in a device on a target real or virtual processor to perform the above reference Figure 3-7 Any method described. Typically, 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 split between program modules as needed in various embodiments. Machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules may be located in local and remote storage media.

[0158] The program code for executing the method of the present application 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, when executed by the processor or controller, enables the functions / operations specified by the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0159] In the context of this application, 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.

[0160] 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, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or apparatuses, or any suitable combination of the foregoing. More specific examples of computer readable storage media would include an electrical connection with one or more conductors, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable reader 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.

[0161] In addition, although the operations are described in a particular order, this should not be construed as requiring such operations to be performed in the particular order shown or in order, or that all operations shown are performed 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 should not be interpreted as limitations on the scope of the application, but rather as descriptions of features that may be specific 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 individually in multiple embodiments or in any suitable sub-combination.

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

Claims

1. A second device for communication, comprising: at least one processor; as well as at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, using at least one processor, cause the second device to: receiving information about a first identifier of a first operator network and a second identifier of a second operator network from a first device included in a second network device, the second device being included in the second network device, and the second network device being configured to provide dual connectivity to a terminal device together with the first network device; Identifying a service termination point associated with the terminal device based on the first identifier; and identifying, based on the second identifier, the second operator network used to serve the terminal device through the second network device, wherein the information about the first and second identifiers is included in a context modification request, and wherein the at least one memory and the computer program code are configured to, with the at least one processor, further cause the second apparatus to: Determining whether the second operator network is compatible with the first operator network based on the determination that the second identifier is different from the first identifier; modifying a context associated with the second operator network for the terminal device in accordance with a determination that the second operator network is compatible with the first operator network; and Based on a determination that the second operator network is incompatible with the first operator network, a context modification response is sent to the first device to reject the context modification request.

2. The device according to claim 1, wherein: The at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to receive the information in the following manner: The first identification and the second identification are received in separate information elements from the first device, the first identification being different from the second identification.

3. The device according to claim 1 or 2, wherein: The at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to receive the information in the following manner: receiving information about the first and second identifiers in a context establishment request from the first device; or Information about the first and second identifications is received in a context modification request from the first device.

4. The device according to claim 1 or 2, wherein: The first arrangement comprises a central unit of the second network device, and the second arrangement comprises a distributed unit of the second network device.

5. The device according to claim 1 or 2, wherein: The first arrangement comprises a central unit control plane entity of the second network device, and the second arrangement comprises a central unit user plane entity of the second network device.

6. A method for communication, comprising: At the second device, receiving information about a first identifier of a first operator network and a second identifier of a second operator network from the first device, the first and second devices being included in a second network device, and the second network device being configured to provide dual connectivity to the terminal device together with the first network device; identifying a service termination point associated with the terminal device based on the first identifier; as well as identifying the second operator network serving the terminal device through the second network device based on the second identifier, The information about the first and second identifiers is included in the context modification request, and the method further comprises: Determining whether the second operator network is compatible with the first operator network based on the determination that the second identifier is different from the first identifier; modifying a context associated with the second operator network for the terminal device in accordance with a determination that the second operator network is compatible with the first operator network; and Based on a determination that the second operator network is incompatible with the first operator network, a context modification response is sent to the first device to reject the context modification request.

7. The method according to claim 6, wherein: Receiving the information includes: The first identification and the second identification are received in separate information elements from the first device, the first identification being different from the second identification.

8. The method according to claim 6 or 7, wherein: Receiving the information includes: receiving information about the first and second identifiers in a context establishment request from the first device; or Information about the first and second identifications is received in a context modification request from the first device.

9. A second device for communication, comprising: means for receiving information about a first identifier of a first operator network and a second identifier of a second operator network from a first device, the first and second devices being included in a second network device, and the second network device being configured to provide dual connectivity to a terminal device together with the first network device; means for identifying a service termination point associated with the terminal device based on the first identifier; as well as a device for identifying the second operator network serving the terminal device through the second network device based on the second identifier, The information about the first and second identifiers is included in the context modification request, and the second device further includes means for: Determining whether the second operator network is compatible with the first operator network based on the determination that the second identifier is different from the first identifier; modifying a context associated with the second operator network for the terminal device based on a determination that the second operator network is compatible with the first operator network; as well as Based on a determination that the second operator network is incompatible with the first operator network, a context modification response is sent to the first device to reject the context modification request.

10. A computer-readable medium comprising program instructions, wherein the program instructions are used to cause a device to at least execute the method according to any one of claims 6 to 8.

11. A computer program product, comprising program instructions, wherein the program instructions are used to cause a device to at least execute the method according to any one of claims 6 to 8.