Detailed Description
Example embodiments are now described in a more complete manner with reference being made to the figures. However, the exemplary embodiments are capable of being embodied in various forms and should not be construed as limited to only these examples, but rather, the embodiments are provided so as to more fully and completely embody the principles of the exemplary embodiments and to fully convey the concept of the exemplary embodiments to those skilled in the art.
Furthermore, the described features, structures, or characteristics of the application may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the application. However, it will be recognized by one skilled in the art that the present inventive arrangements may be practiced without all of the specific details of the embodiments, that one or more specific details may be omitted, or that other methods, elements, devices, steps, etc. may be used.
In the present embodiment, the term "module" or "unit" refers to a computer program or a part of a computer program having a predetermined function and working together with other relevant parts to achieve a predetermined object, and may be implemented in whole or in part by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Also, a processor (or multiple processors or memories) may be used to implement one or more modules or units. Furthermore, each module or unit may be part of an overall module or unit that incorporates the functionality of the module or unit.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
It should be noted that the term "plurality" as used herein means two or more. "and/or" describes the association relationship of the association object, and indicates that there may be three relationships, for example, a and/or B may indicate that there are three cases of a alone, a and B together, and B alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
With the continuous development of mobile communication technology, in the evolution process from 4G to 5G, the coverage area, capacity and speed of the network are all significantly improved. However, achieving smooth transitions and efficient interoperability between different mobile communication technologies remains a technical challenge. In the 4G era, the introduction of a long term evolution (Long Term Evolution, LTE) Femto and CSG mechanism provides flexible and various solutions for the access of small cells, and meets the network coverage and capacity requirements in hot spot scenes such as families, enterprises and the like. However, in the early development stage of 5G, a mechanism similar to LTE Femto is not directly introduced due to restrictions of standard formulation and technology implementation, and although a CAG mechanism is introduced in 5G, seamless handover between 4G and 5G networks is still not achieved.
In particular, LTE Femto cells in 4G networks bring better network experience for home and enterprise users by providing a small range of coverage and flexible access control. However, in 5G networks, handover between LTE Femto cells and 5G CAG cells becomes difficult due to the lack of a corresponding support mechanism. The limitation not only affects the network use flexibility of users in hot spot scenes such as families, enterprises and the like, but also restricts the interoperability between 4G and 5G networks, thereby affecting the performance of the whole network.
Wherein the CSGs represent a set of users that can connect to the home base station, each CSG has a unique CSG ID, and the UE can maintain a CSG ID list of the CSG to which it belongs. Only the CSG cell corresponding to the CSG ID in this list is accessible to the UE. While CAGs are similar to CSG, a CAG represents a group of user equipments that can access a certain CAG cell, a CAG is typically associated with an NPN. In the PNI-NPN scenario, CAG is used for access control. By means of CAG ID list + network slice, end-to-end resource dedication can be achieved such that NPN exists as one slice of public land mobile network (Public Land Mobile Network, PLMN). This configuration enables the network to more flexibly meet the needs of different users, especially in scenarios where specific security or isolation is required.
In an exemplary application scenario of the present application, a non-roaming architecture for interworking between an evolved packet core network (Evolved Packet Core, EPC)/evolved UMTS terrestrial radio access network (Evolved UMTS Terrestrial Radio Access Network, E-UTRAN) network and a 5G system (5 gsystem,5 gs) is shown in fig. 1. In the architecture, the UE can access a Mobility management entity (Mobility MANAGEMENT ENTITY, MME) in the 4G network through the E-UTRAN, the MME is connected to a serving gateway (SERVING GATEWAY, SGW) through an S11 interface, and the SGW is one of important network elements in the EPC and is responsible for forwarding and routing functions of user plane data.
Meanwhile, the UE may access a next generation radio access network (Next Generation Radio Access Network, NG-RAN), and the UE may connect with an access and mobility management function (ACCESS AND Mobility Management Function, AMF) through an N1 interface, and the NG-RAN may connect to the AMF through an N2 interface.
The SGW is connected to a User Plane function (User Plane Function, UPF) +packet data Network Gateway User Plane (PACKET DATA Network Gateway-User Plane, PGW-U) through an S5 User Plane interface (i.e., S5-U), and to a session management function (Session Management Function, SMF) +packet data Network Gateway Control Plane (PACKET DATA Network Gateway-Control Plane, PGW-C) through an S5 Control Plane interface (S5-C). The NG-RAN is connected to the upf+pgw-U through an N3 interface, the AMF is connected to the smf+pgw-C through an N11 interface, and is connected to a Policy control Function (Policy Control Function, PCF) +policy and charging Rules Function (PCRF) through an N15 interface. smf+pgw-C connects to home subscriber server (Home Subscriber Server, HSS) +unified data management (Unified DATA MANAGEMENT, UDM) through N10 interface.
In the system architecture shown in fig. 1, the N26 interface is an important component, and the N26 interface is a Core Network (CN) interface between the MME in 4G and the AMF in 5GS, for implementing interworking between EPC and NG Core networks (e.g., 5G Core networks). Support of the N26 interface is optional for interworking, and N26 supports the subset of functions supported on S10.
In addition, SMF+PGW-C and UPF+PGW-U are entities dedicated to interworking between 5GS and EPC, but this is also optional. UEs not constrained by 5GS and EPC interworking may be served by entities not dedicated to interworking, such as PGW or SMF, UPF, etc.
With further development and application of the 5G technology, how to realize effective switching between LTE Femto cells and 5GCAG cell, and improve interoperability between 4G and 5G networks becomes a technical problem to be solved in the current mobile communication field. This requires not only intensive research into new handover mechanisms and technical solutions, but also consideration of how to ensure security, stability and efficiency in the handover process, so as to provide better network experience and quality of service for the user.
Based on this, the technical solution of the embodiment of the present application proposes a new cross-system cell switching solution, so that the network side device may acquire the CSG and CAG supporting situation of the UE, and when the UE performs cross-system (e.g., 4G system to 5G system or 5G system to 4G system) cell switching processing, only if it is determined that the UE can support CSG and CAG simultaneously, the cross-system cell switching processing is performed on the UE, thereby avoiding increasing unnecessary signaling overhead of the network due to the cross-system cell switching processing on the UE that does not support CSG or CAG, and implementing the switching processing between CSG cells and CAG cells of the UE, so as to improve the flow transmission flexibility in hot scenarios such as home environments, enterprise environments, and the like.
The implementation details of the technical scheme of the embodiment of the application are described in detail below:
Fig. 2 shows a flowchart of a cross-system cell handover method according to an embodiment of the present application, where the cross-system cell handover method may be performed by a network side device, which may be an access network device, such as a base station, etc., or may be a core network device, such as an MME, PGW-C, PCRF, AMF, SMF, PCF, etc., or may be performed by other devices that implement similar functions. Referring to fig. 2, the method for switching cells across systems at least includes S210 to S220, which are described in detail as follows:
In S210, the support situation of the user for the closed subscriber group CSG and the closed access group CAG is acquired.
In some optional embodiments, the network side device may acquire the support condition of the user equipment for the closed subscriber group CSG and the closed access group CAG by receiving capability information reported by the user equipment, where the capability information is used to indicate the support condition of the user equipment for the CSG and the CAG.
It should be noted that CSG is generally applied to 4G networks, and refers to a group of subscribers allowed to access one or more specific cells, which are limited and conditional when accessing subscribers, unlike the characteristics of a common cell that allow access to all legal subscribers (and roaming subscribers) of an operator. In practical applications, CSG helps to achieve more refined network control and user management, especially in home base stations or enterprise networks, by restricting users accessing a specific cell, operators can provide more customized services while ensuring network security and efficient use of resources.
CAG may be used to identify and manage a group of users that are allowed to access a particular cell (i.e., CAG cell), and may be used in the context of PNI-NPN in general, and in 5G networks in particular, to prevent the UE from automatically selecting and registering from locations that do not provide NPN access or locations that do not allow the UE to access NPN. Each CAG cell only allows the UE subscribed to the target CAG to access, so that the fine control on network access is realized, and the control mechanism is helpful to ensure the effective utilization of network resources and provide safer and more reliable network services.
Optionally, the supporting condition of the user equipment for the CSG may be whether the user equipment supports access to the CSG cell, i.e. whether the user equipment has the capability of accessing to the CSG cell, and the supporting condition of the user equipment for the CAG may be whether the user equipment supports access to the CAG cell, i.e. whether the user equipment has the capability of accessing to the CAG cell, which mainly reflects the cell access capability of the UE for different communication systems.
Optionally, when the user equipment reports the support condition of CSG and CAG to the network side device, the user equipment may multiplex the existing signaling, or may use a redefined signaling message. For example, the ue may indicate the supporting situation of CSG and CAG by one or more flag bits in signaling, for example, when the signaling is indicated by two flag bits, if the two flag bits have a value of "00", it may indicate that the ue supports neither CSG nor CAG, if the two flag bits have a value of "01", it may indicate that the ue does not support CSG but supports CAG, if the two flag bits have a value of "10", it may indicate that the ue supports CSG but does not support CAG, and if the two flag bits have a value of "11", it may indicate that the ue supports neither CSG nor CAG. In other embodiments of the present application, the capability information of the user equipment may be indicated by more flag bits, or may be indicated by other manners.
With continued reference to fig. 2, in S220, if it is determined that the user equipment supports both CSG and CAG according to the support situation, a cell handover process is performed for the user equipment across systems.
In some alternative embodiments, if the user equipment supports both CSG and CAG, then the explanation may be that the user equipment may be subject to a cross-system cell handover process. For example, when the user equipment performs data transmission through the CSG cell, if it is determined that the user equipment needs to be triggered to perform cross-system cell handover processing, the user equipment may be controlled to switch to the CAG cell for data transmission, or when the user equipment performs data transmission through the CAG cell, if it is determined that the user equipment needs to be triggered to perform cross-system cell handover processing, the user equipment may be controlled to switch to the CSG cell for data transmission.
In some optional embodiments, when performing cross-system cell handover processing on the user equipment, at least one of subscription information of the user equipment for the cross-system cell handover processing and access configuration information of the user equipment may be further considered to determine whether the user equipment is capable of performing the cross-system cell handover processing. Optionally, the subscription information of the ue for the cross-system cell handover processing refers to whether the ue signs up for the cross-system cell handover service, and if the ue signs up for the cross-system cell handover service, it is indicated that the ue may perform the cross-system cell handover processing on the subscription information level. The access configuration information of the user equipment refers to whether the user equipment is allowed to access to the CAG cell or the CSG cell, which is a determination from the access configuration level as to whether the user equipment is capable of performing a cross-system cell handover process.
Optionally, if the ue supports CSG and CAG simultaneously and determines that the ue is capable of performing a cross-system cell handover process according to the above information, a cross-system cell handover procedure may be initiated for the ue.
In some alternative embodiments, if the ue cannot support CSG and CAG simultaneously, when it is determined that the ue needs to be triggered to perform cell handover, the target cell for the ue handover is adjusted to a cell of the same system, or a cell handover procedure is not initiated. For example, when the ue performs data transmission through the CSG cell, if it is determined that the ue needs to be triggered to perform cell handover, but since the ue does not support CAG, the ue may be controlled to switch to access to another CSG cell, or cell handover may not be performed. For another example, when the ue performs data transmission through the CAG cell, if it is determined that the ue needs to be triggered to perform cell switching, but the ue may be controlled to switch to other CAG cells because the ue does not support CSG, or cell switching may not be performed.
In some optional embodiments, the network side device may acquire parameter configuration information for performing a cross-system cell handover process, so as to perform the cross-system cell handover process on the user equipment according to the parameter configuration information. Optionally, the parameter configuration information comprises a list of cross-system cells that allow handover. The technical solution of the embodiment enables the network side device to implement the cross-system cell switching processing of the user device through the parameter configuration information, for example, the user device can be determined to which cell to switch according to the cross-system cell list allowed to switch. Specifically, when the user equipment performs data transmission through the CSG cell, the parameter configuration information of the network side device may include a CAG cell list that allows handover, and when the network side device determines that the user equipment needs to perform cell handover, the network side device may select, according to the CAG cell list that allows handover, a CAG cell to which the user equipment is to be handed over.
In some alternative embodiments, the parameter configuration information for performing the cross-system cell handover process may further include handover priorities of cells included in the cross-system cell list. Optionally, when the user equipment performs data transmission through the CSG cell, the parameter configuration information of the network side device may include a CAG cell list allowed to be switched, and when the network side device determines that the user equipment needs to perform cell switching, the network side device may select, according to the CAG cell list allowed to be switched and priorities of the CAG cells in the list, a CAG cell to which the user equipment is to be switched (e.g., a CAG cell with a highest priority may be selected).
Optionally, the cross-system cell list may only include the cross-system cells allowed to be switched, or may include a mapping relationship between the current system cell and the cross-system cells allowed to be switched. For example, if the cell where the user equipment is currently located is a CSG cell, the inter-system cell list may include CAG cells allowed to be switched to, or may also include a mapping relationship between each CSG cell and a corresponding CAG cell allowed to be switched to.
In some alternative embodiments, the list of cross-system cells that allow handover may be determined based on at least one of cross-system cells adjacent to the location of the cell where the user equipment is currently located, cell frequency limitation information for cross-system handover, and cell handover policies for cross-system.
Optionally, the cross-system cell adjacent to the location of the cell where the user equipment is currently located refers to the cross-system cell where the user equipment is currently located, for example, the cell where the user equipment is currently located is a CSG cell, and then, according to the location information of the CSG cell, the adjacent CAG cell or the CAG cell with overlapping coverage area may be used as the cross-system cell adjacent to the location of the cell where the user equipment is currently located.
Optionally, the cell frequency limitation information of the cross-system handover refers to frequency limitation of the ue when performing the cross-system handover, for example, the cell where the ue is currently located is a CSG cell, the cell frequency is 900Mhz, the cell frequency limitation information is a cell where handover is prohibited to 3.5Ghz, and even if there is a neighboring CAG cell near the location of the ue, if the frequency of the CAG cell is 3.5Ghz, it is indicated that the CAG cell is a cross-system cell that does not allow handover.
Optionally, the cross-system cell handover policy refers to policy limitation information of the ue when performing cross-system handover, for example, the cell where the ue is currently located is a CSG cell, but the 5G traffic of the ue is already exhausted, so that the ue is not allowed to be handed over to the CAG cell, or if the cell where the ue is currently located is a CSG cell, but the traffic of a CAG cell adjacent to the CSG cell where the ue is located is busy, so that the ue is not allowed to be handed over to the CAG cell.
In some optional embodiments, the network side device may receive neighbor cell measurement information reported by the user equipment, and may generate an automatic neighbor relation (Automatic Neighbor Relation, ANR) table according to the neighbor cell measurement information. Alternatively, the technical solution of this embodiment may be performed by the base station. For example, it may be E-UTRAN, eNB, NG-RAN, etc.
It should be noted that, the ANR function may automatically create and update a neighbor relation between a serving cell and a neighbor cell, so as to support cell handover, and the ANR function may reduce time required for configuration and planning of a network, optimize network performance, further reduce workload of manually configuring the neighbor relation, and solve the problems of high cost, low optimization efficiency and the like in a conventional neighbor optimization manner.
In some optional embodiments, the network side device may receive neighbor cell measurement information reported by the user equipment, and may maintain at least one of CSG and CAG corresponding to the user equipment according to the neighbor cell measurement information. Alternatively, the technical solution of this embodiment may be performed by the base station, or may be performed by a core network device (such as MME, AMF, etc.).
In some optional embodiments, the network side device (e.g., a base station) may receive neighbor cell measurement information reported by the user equipment, and may report an automatic neighbor relation table generated according to the neighbor cell measurement information to a core network element (e.g., MME, AMF, etc.), so that the core network element maintains at least one of CSG and CAG corresponding to the user equipment according to the automatic neighbor relation table.
In some optional embodiments, the network side device (e.g., a base station) may receive neighbor cell measurement information reported by the user equipment, and may report the neighbor cell measurement information to a core network element (e.g., MME, AMF, etc.), so that the core network element maintains at least one of CSG and CAG corresponding to the user equipment according to the automatic neighbor relation table.
In some optional embodiments, the network side device may receive neighbor cell measurement information reported by the user equipment, where the neighbor cell measurement information is obtained by the user equipment by performing cell measurement processing based on one or more of application layer information, location information, and system information of a serving cell.
Alternatively, the user equipment may perform cell measurement based on application or service related data, such as quality of service (Quality of Service, qoS) requirements, etc., which may reflect the current communication needs and status of the UE, such as the current network status failing to meet the communication needs, etc.
Alternatively, the user equipment may perform cell measurement processing based on the location information, where if it is determined that there is a neighboring cell in the vicinity, based on the location where the user equipment is located, cell measurement processing may be performed to find whether there is a CAG cell or a CSG cell in the vicinity.
Alternatively, the cell measurement processing performed by the ue based on the system information of the serving cell may be that, based on the information (such as the frequency point, bandwidth, etc. of the current serving cell) included in the system information of the serving cell, measurements are performed at the frequency points adjacent to the serving cell to find whether there is a CAG cell or a CSG cell in the vicinity.
In some optional embodiments, the network side device may send information of the frequency to be measured to the ue to enable the ue to perform cell measurement processing on the frequency to be measured, and then receive neighbor cell measurement information fed back by the ue to perform cell measurement processing on the frequency to be measured. Namely, the technical scheme of the embodiment enables the user equipment to perform cell measurement processing under the configuration of the network side.
The technical solution of the embodiment of the present application is explained above from the perspective of the network side device, and the technical solution of the embodiment of the present application is explained in detail below from the perspective of the UE with reference to fig. 3:
Fig. 3 shows a flow chart of a cross-system cell handover method according to an embodiment of the application, which may be performed by a user equipment or by other devices implementing similar functions. Referring to fig. 3, the method for switching cells across systems at least includes S310 to S320, which are described in detail as follows:
in S310, the support situation of the user for the closed subscriber group CSG and the closed access group CAG is obtained.
Alternatively, the user equipment may determine the support situation for CSG and CAG according to its own capability information. The relevant descriptions of CSG and CAG may refer to the technical solutions of the foregoing embodiments, and will not be described herein.
In S320, the supporting conditions of the user equipment for CSG and CAG are reported to the network side device, so that when the network side device determines that the user equipment supports both CSG and CAG, the network side device performs a cross-system cell handover process for the user equipment.
Optionally, when the user equipment reports the support condition of CSG and CAG to the network side device, the user equipment may multiplex the existing signaling, or may use a redefined signaling message. For example, the ue may indicate the supporting situation of CSG and CAG by one or more flag bits in signaling, for example, when the signaling is indicated by two flag bits, if the two flag bits have a value of "00", it may indicate that the ue supports neither CSG nor CAG, if the two flag bits have a value of "01", it may indicate that the ue does not support CSG but supports CAG, if the two flag bits have a value of "10", it may indicate that the ue supports CSG but does not support CAG, and if the two flag bits have a value of "11", it may indicate that the ue supports neither CSG nor CAG. In other embodiments of the present application, the capability information of the user equipment may be indicated by more flag bits, or may be indicated by other manners.
Optionally, the process of performing the cross-system cell handover processing on the user equipment by the network side device may refer to the technical solution of the foregoing embodiment, which is not described herein.
According to the technical scheme of the embodiment of the application, the network side equipment can acquire the supporting condition of the UE on the CSG and the CAG, and when the UE performs the cell switching processing of a cross-system (such as a 4G system to a 5G system or a 5G system to a 4G system), the cell switching processing of the cross-system is performed on the user equipment only if the user equipment is determined to simultaneously support the CSG and the CAG, so that unnecessary signaling overhead of a network is increased when the user equipment which does not support the CSG or the CAG performs the cell switching processing of the cross-system, the switching processing of the user equipment between the CSG cell and the CAG cell is realized, and the flow transmission flexibility of the user equipment in hot spot scenes such as a home environment, an enterprise environment and the like can be improved.
The implementation details of the technical solution of the embodiment of the present application are further described below with reference to fig. 4 to 6:
In one embodiment of the present application, to enable a UE to perform a cross-system small cell handover, i.e., a handover between a CSG cell and a CAG cell, the UE, E-UTRAN, NG-RAN, MME, PGW-C, PCRF, AMF, SMF, PCF, etc. in the system architecture shown in fig. 1 may be enhanced.
Optionally, the UE needs to notify the corresponding network elements on the network side of the capability information of the LTE CSG and the 5G CAG, such as MME and AMF (the following embodiments take MME and AMF as examples to illustrate, and PGW-C, PCRF, SMF, PCF may also be used in other embodiments of the present application). The MME and AMF may determine whether to support such a cross-system small cell handover based on capability information of the UE. Specifically, such a cross-system small cell handover process may be performed if the UE supports both CAG and CSG, and may not be performed if the UE does not support CAG or CSG, to avoid blindly performing handover and increasing overhead of network signaling.
Optionally, the network side (such as a base station, MME, AMF, etc.) may also determine whether to initiate a handover of a small cell across systems according to subscription information of the UE (i.e. whether to sign up for a handover function across small cells of systems), and access configuration information (i.e. whether to allow access to CSG or CAG). For example, when the network side receives a measurement report or other information of the UE and needs to trigger cell handover, if the UE is found not to support CAG or CSG, or it is determined that cross-system small cell handover cannot be performed according to subscription information and/or access configuration information, handover is not initiated (only cross-system small cells are suitable for a target cell capable of handover), or a handover target is directed to the cross-system small cells (when the target cell capable of handover also includes other cells other than the cross-system cells).
In one embodiment of the present application, to perform a cross-system small cell handover at a network location where a cross-system small cell handover may occur, a base station (e.g., E-UTRAN, NG-RAN, etc.), a core network (e.g., MME, AMF, etc.), or an operation and maintenance management (Operation Administration AND MAINTENANCE, OAM) network element may also be enhanced. Specifically, from the perspective of network topology, when there is a small cell (such as coverage area adjacent or overlapping) around a cell, the parameter configuration of the small cell handover can be performed.
Specifically, as shown in fig. 4, according to the coverage of the 4G LTE femto cell, there are CAG cell 2 and CAG cell 3 in its neighboring area, in which case a cross-system small cell handover may be initiated for the UE.
In some alternative embodiments, in addition to being geographically adjacent, it is also desirable to incorporate inter-frequency handover limitations, handover policies, etc., to ascertain whether parameter configuration for cross-system small cell handover is required.
Optionally, the inter-frequency handover restriction is a frequency restriction of the UE when performing the inter-system handover, for example, the cell where the UE is currently located is a CSG cell, the cell frequency is 900Mhz, and the cell frequency restriction information is a cell where handover is prohibited to 3.5Ghz, so even if there is a neighboring CAG cell near the location of the UE, if the frequency of the CAG cell is 3.5Ghz, it is indicated that the CAG cell is a inter-system cell that does not allow handover.
Optionally, the handover policy refers to policy limitation information when the UE performs a cross-system handover, for example, the cell where the UE is currently located is a CSG cell, but the 5G traffic of the UE is already exhausted, so that the UE is not allowed to be handed over to the CAG cell, or if the cell where the UE is currently located is a CSG cell, but the traffic of a CAG cell adjacent to the CSG cell where the UE is located is busy, so that the UE is not allowed to be handed over to the CAG cell.
In some alternative embodiments, the parameters for performing a cross-system small cell handover may include, but are not limited to, a cross-system cell list, a cell handover priority, and the like. It should be noted that the cross-system cell list may include at least one of whether there is a cross-system small cell, a cross-system cell allowing handover, a handover mapping relationship between a CSG cell and a CAG cell (for example, a cell where the user equipment is currently located is a CSG cell, and then the cross-system cell list may include a CAG cell allowing handover, or may also include a mapping relationship between each CSG cell and a corresponding CAG cell allowing handover). Alternatively, the parameters for performing a cross-system small cell handover may also contain an ANR table.
Alternatively, if there is a cross-system small cell in the cross-system cell list that allows handover, the base station may configure the UE to measure the cell, triggering a cell handover process.
In some optional embodiments, the UE may also measure the cell, and then the network side device (such as the base station, MME, AMF, etc.) may dynamically update the ANR table based on the measurement report of the UE, or update the above-mentioned cross-system cell list (the cross-system cell list may include cross-system cells that allow handover, may also include a handover mapping table between CSG cells and CAG cells, etc.), or update CSG or CAG, etc.
Alternatively, the measurement report of the UE may include a measurement report spontaneous by the UE, or may include the base station configuring the UE to perform the measurement report. If the measurement report is spontaneous, the UE may measure the neighbor cell based on application layer information and other information (such as location information, whether a cross-system small cell may exist nearby, etc.), or the UE may discover information of the neighbor cell by detecting system information of the serving cell, and then the UE reports CSG or CAG cell information in the neighbor cell discovered by measurement to the serving base station. The serving base station may dynamically update the ANR table according to the information reported by the UE measurement, or update the above-mentioned cross-system cell list, or update the CSG or CAG, etc. Optionally, the serving base station may report one or more of the ANR table, the information reported by the UE, and the information such as CSG or CAG maintained by the base station to the core network device (e.g., MME, AMF, etc.), so that the core network device maintains the CSG or CAG corresponding to the UE, and if the core network device also maintains the cross-system cell list, the core network device may also update the maintained cross-system cell list.
Optionally, when the base station configures the UE to perform measurement report, the base station may configure the UE to perform inter-frequency measurement, the UE may find that a cross-system small cell exists on the inter-frequency through measurement, and may acquire related information, such as CSG, CAG, etc., through a GAP or other mechanism, and then the UE reports CSG or CAG cell information in a neighbor cell found by measurement to the serving base station. The serving base station may dynamically update the ANR table according to the information reported by the UE measurement, or update the above-mentioned cross-system cell list, or update the CSG or CAG, etc. Optionally, the serving base station may report one or more of the ANR table, the information reported by the UE, and the information such as CSG or CAG maintained by the base station to the core network device (e.g., MME, AMF, etc.), so that the core network device maintains the CSG or CAG corresponding to the UE, and if the core network device also maintains the cross-system cell list, the core network device may also update the maintained cross-system cell list.
Alternatively, the operator may support configuring corresponding CSG and CAG information for the UE simultaneously to support cross-system small cell access and handover interoperability for a certain area.
The following describes a handover procedure between an LTE CSG cell and a 5G CAG cell. As shown in fig. 5, a procedure of switching an LTE CSG cell to a 5G CAG cell according to one embodiment of the present application includes the steps of:
s501, the UE accesses the EPC through the LTE CSG cell to perform data transmission.
S502, the 4G side judges that the UE supports CAG, and can trigger system switching.
It should be noted that, since the UE has already accessed to the LTE CSG cell, if the 4G side determines that the UE also supports CAG, it is indicated that the UE may support CSG and CAG at the same time. Optionally, the 4G side may determine whether to initiate a handover of a small cell across systems according to subscription information (i.e. whether to sign up for a handover function across small cells of systems) and access configuration information (i.e. whether to allow access to CSG or CAG) of the UE, in addition to determining whether the UE supports CSG and CAG simultaneously according to capability information of the UE. For specific determination, reference may be made to the technical solutions of the foregoing embodiments.
S503,4G side carries out parameter configuration of cross-system small cell switching and carries out small cell switching.
Alternatively, parameters for performing a cross-system small cell handover may include, but are not limited to, a cross-system cell list, a cell handover priority, and the like. The cross-system cell list may indicate whether or not a cross-system small cell exists, or may indicate a cross-system cell that allows handover, and may include an ANR table or other cross-system cells that can allow handover.
And S504, reporting and updating related parameters by the 4G side according to the measurement of the UE.
Optionally, the 4G side (e.g. E-UTRAN, MME, etc.) may dynamically update the ANR table based on the measurement report of the UE, or update the above-mentioned cross-system cell list, or update the CSG or CAG, etc.
It should be noted that, the execution order of S504 and the other steps is not critical, that is, S504 may be performed before the other steps shown in fig. 5, may be performed after the other steps shown in fig. 5, or may be performed simultaneously with the other steps shown in fig. 5.
And S505, completing the switching, and accessing 5GS by the UE through the 5G CAG cell for data transmission.
As shown in fig. 6, a procedure of switching a 5G CAG cell to an LTE CSG cell according to one embodiment of the present application includes the steps of:
S601, UE accesses 5GS through 5G CAG cell to transmit data.
S602, if the 5G side judges that the UE supports CSG, the system switching can be triggered.
It should be noted that, since the UE has already accessed to the 5G CAG cell, if the 5G side determines that the UE also supports CSG, it is indicated that the UE may support CSG and CAG simultaneously. Optionally, the 5G side may determine whether to initiate a handover of a small cell across systems according to subscription information (i.e. whether to sign up for a handover function across small cells of systems) and access configuration information (i.e. whether to allow access to CSG or CAG) of the UE, in addition to determining whether the UE supports CSG and CAG simultaneously according to capability information of the UE. For specific determination, reference may be made to the technical solutions of the foregoing embodiments.
S603, the 5G side performs parameter configuration of cross-system small cell switching and performs small cell switching.
Alternatively, parameters for performing a cross-system small cell handover may include, but are not limited to, a cross-system cell list, a cell handover priority, and the like. The cross-system cell list may indicate whether or not a cross-system small cell exists, or may indicate a cross-system cell that allows handover, and may include an ANR table or other cross-system cells that can allow handover.
And S604, reporting and updating related parameters by the 5G side according to the measurement of the UE.
Alternatively, the 5G side (e.g., NG-RAN, AMF, etc.) may dynamically update the ANR table based on the measurement report of the UE, or update the above-mentioned cross-system cell list, or update the CSG or CAG, etc.
It should be noted that, the execution order of S604 and the other steps is not critical, that is, S604 may be performed before the other steps shown in fig. 6, may be performed after the other steps shown in fig. 6, or may be performed simultaneously with the other steps shown in fig. 6.
S605, switching is completed, and the UE accesses the EPS through the LTE CSG cell to perform data transmission.
It should be noted that, the technical solution of the embodiment of the present application may be implemented based on the N26 interface shown in fig. 1, and in other embodiments of the present application, the technical solution of the embodiment of the present application is also applicable to an application scenario without an N26 interface.
In summary, the technical scheme of the embodiment of the application supports the high-efficiency switching of the UE between the LTE CSG and the 5G CAG cells, avoids unnecessary signaling overhead, realizes high-efficiency cross-system small cell switching, improves the flow transmission flexibility in hot spot scenes such as home environments, enterprise environments and the like, and is beneficial to improving the operation efficiency of the 5G and 4G systems.
The following describes an embodiment of the apparatus of the present application, which may be used to perform the cell handover method across systems in the above embodiment of the present application. For details not disclosed in the embodiment of the apparatus of the present application, please refer to the embodiment of the cross-system cell handover method described above.
Fig. 7 shows a block diagram of a cross-system cell switching apparatus according to an embodiment of the present application, where the cross-system cell switching apparatus may be applied to a network side device, and the network side device may be an access network device, such as a base station, etc., or may be a core network device, such as an MME, an AMF, etc., or may be another device that performs a similar function.
Referring to fig. 7, a cross-system cell switching apparatus 700 according to an embodiment of the present application includes an acquisition unit 702 and a processing unit 704.
The acquiring unit 702 is configured to acquire a supporting situation of the user equipment for the closed subscriber group CSG and the closed access group CAG, and the processing unit 704 is configured to perform a cross-system cell handover process for the user equipment if it is determined that the user equipment supports both the CSG and the CAG according to the supporting situation.
In some embodiments of the present application, based on the foregoing solution, the obtaining unit 702 is configured to receive capability information reported by the ue, where the capability information is used to indicate a supporting situation of the ue for the CSG and the CAG.
In some embodiments of the present application, based on the foregoing solutions, the processing unit 704 is configured to initiate a cross-system cell handover procedure for the ue if it is determined that the ue is capable of performing cross-system cell handover processing according to at least one of subscription information of the ue for cross-system cell handover processing and access configuration information of the ue.
In some embodiments of the present application, based on the foregoing solution, the processing unit 704 is further configured to, if the ue cannot support the CSG and the CAG simultaneously, adjust a target cell for handover of the ue to a cell of the same system or not initiate a cell handover procedure when it is determined that the ue needs to be triggered to perform cell handover.
In some embodiments of the present application, based on the foregoing solution, the obtaining unit 702 is further configured to obtain parameter configuration information for performing a cross-system cell handover process, so as to perform the cross-system cell handover process on the user equipment according to the parameter configuration information, where the parameter configuration information includes a cross-system cell list that allows handover.
In some embodiments of the present application, based on the foregoing scheme, the parameter configuration information further includes a handover priority of each cell included in the inter-system cell list.
In some embodiments of the present application, the list of handover-allowed cells is determined based on at least one of a cross-system cell adjacent to a location of a cell where the user equipment is currently located, cell frequency limitation information for cross-system handover, and a cross-system cell handover policy based on the foregoing scheme.
In some embodiments of the present application, based on the foregoing solution, the cell handover apparatus 700 of the cross-system further includes a receiving unit configured to receive neighbor cell measurement information reported by the ue, and perform at least one of the following processing procedures:
Generating an automatic neighbor relation table according to the neighbor measurement information;
maintaining at least one of CSG and CAG corresponding to the user equipment according to the neighbor cell measurement information;
Reporting an automatic neighbor relation table generated according to the neighbor cell measurement information to a core network element, so that the core network element maintains at least one of CSG and CAG corresponding to the user equipment according to the automatic neighbor relation table;
reporting the neighbor cell measurement information to a core network element, so that the core network element maintains at least one of CSG and CAG corresponding to the user equipment according to the automatic neighbor relation table.
In some embodiments of the present application, based on the foregoing solution, the receiving unit is configured to receive neighbor cell measurement information obtained by the ue performing cell measurement processing based on one or more of application layer information, location information, and system information of a serving cell.
In some embodiments of the present application, based on the foregoing solutions, the receiving unit is configured to send information of a frequency to be measured to the ue, so that the ue performs cell measurement processing on the frequency to be measured, and receive neighbor cell measurement information fed back by the ue performing cell measurement processing on the frequency to be measured.
In some embodiments of the present application, based on the foregoing solution, the processing unit 704 is configured to control, when the ue performs data transmission through the CSG cell, the ue to switch to the CAG cell for data transmission if it is determined that the ue needs to be triggered to perform a cross-system cell switching process, or
When the user equipment performs data transmission through the CAG cell, if the user equipment is determined to be required to trigger the cross-system cell switching processing, the user equipment is controlled to switch into the CSG cell for data transmission.
Fig. 8 shows a block diagram of a cross-system cell switching device according to an embodiment of the application, which can be applied to a user equipment or to other devices implementing similar functions.
Referring to fig. 8, a cross-system cell switching apparatus 800 according to an embodiment of the present application includes an acquisition unit 802 and a transmission unit 804.
The acquiring unit 802 is configured to acquire a supporting situation of a user equipment on a closed subscriber group CSG and a closed access group CAG, and the transmitting unit 804 is configured to report the supporting situation of the user equipment on the CSG and the CAG to a network side device, so that the network side device performs a cross-system cell handover process on the user equipment when determining that the user equipment supports the CSG and the CAG simultaneously.
Fig. 9 shows a schematic diagram of a computer system suitable for implementing an electronic device, which may be a network-side device or a user device in the foregoing embodiments, according to an embodiment of the present application.
It should be noted that, the computer system 900 of the electronic device shown in fig. 9 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.
As shown in fig. 9, the computer system 900 may include a central processing unit (Central Processing Unit, CPU) 901 which may perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 902 or a program loaded from a storage portion 908 into a random access Memory (Random Access Memory, RAM) 903, for example, performing the methods described in the above embodiments. In the RAM 903, various programs and data required for system operation are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other through a bus 904. An Input/Output (I/O) interface 905 is also connected to bus 904.
The following components may be connected to the I/O interface 905, an input section 906 including a keyboard, a mouse, and the like, an output section 907 including such as a Cathode Ray Tube (CRT), a Liquid crystal display (Liquid CRYSTAL DISPLAY, LCD), and the like, and a speaker, a storage section 908 including a hard disk, and the like, and a communication section 909 including a network interface card such as a LAN (Local Area Network) card, a modem, and the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 910 so that a computer program read out therefrom is installed into the storage section 908 as needed.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium for performing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909 and/or installed from the removable medium 911. When the computer program is executed by a Central Processing Unit (CPU) 901, various functions defined in the system of the present application are performed.
It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of a computer-readable storage medium may include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), a flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with a computer-readable computer program embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer programs.
The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
As another aspect, the present application also provides a computer-readable medium that may be included in the electronic device described in the above embodiment, or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more computer programs which, when executed by the electronic device, cause the electronic device to implement the methods described in the above embodiments.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a mobile hard disk, etc.) or on a network, comprising several instructions for causing an electronic device to perform the method according to the embodiments of the present application.
For example, the electronic device may be a network side device, and then the network side device may perform the cross-system cell switching method shown in fig. 2, and for another example, the electronic device may be a user device, and then the user device may perform the cross-system cell switching method shown in fig. 3.
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.