WO2020192387A1 - 一种请求处理方法、相关装置及系统 - Google Patents

一种请求处理方法、相关装置及系统 Download PDF

Info

Publication number
WO2020192387A1
WO2020192387A1 PCT/CN2020/078110 CN2020078110W WO2020192387A1 WO 2020192387 A1 WO2020192387 A1 WO 2020192387A1 CN 2020078110 W CN2020078110 W CN 2020078110W WO 2020192387 A1 WO2020192387 A1 WO 2020192387A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
request message
type
addition request
information
Prior art date
Application number
PCT/CN2020/078110
Other languages
English (en)
French (fr)
Inventor
顾晨
李冠臣
葛欣明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020192387A1 publication Critical patent/WO2020192387A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • This application relates to the field of communications, and in particular to a request processing method, related device and system.
  • New features are constantly being introduced in wireless communication systems, and there are more and more brands and models of terminal devices. Different types of terminals may support different features, that is, not all features introduced by wireless communication systems can be used by all types. Terminal support. When the characteristics used by the base station are not supported by the terminal equipment, abnormal call drops are prone to occur, which reduces system performance.
  • the 3GPP protocol defines the UE type information transfer process between the mobility management entity (MME) and the evolutional node B (eNB or eNodeB). It also defines the transfer process of the type information of the terminal equipment between the eNB and the eNB, which can facilitate the eNB to perform differentiated management of different types of terminal equipment.
  • MME mobility management entity
  • eNB evolutional node B
  • eNodeB evolutional node B
  • the wireless communication system has begun to evolve into the fifth generation (5G) wireless communication system.
  • the terminal equipment transmits data through the dual connection (DC) communication system formed by the LTE system and the NR system.
  • DC dual connection
  • the current protocol There is no definition of how the base station (gNB) in the new radio (NR) system obtains the type information of the terminal equipment (UE). Therefore, a set of solutions that can help the gNB obtain the type information of the terminal equipment Urgently awaiting launch.
  • the embodiments of the present application provide a request processing method, related device, and system.
  • the first base station can obtain UE type information of at least one UE from the first base station addition request sent by the second base station, and the second base station is provided to obtain the UE type. Information scheme.
  • an embodiment of the present application provides a request processing method.
  • the first base station can receive the first base station addition request message sent by the second base station.
  • the first base station addition request is used to indicate that the first base station is about to access
  • the UE prepares radio resources.
  • the first base station determines the type of the UE according to the UE type information in the first base station addition request message, where the first base station is an NR base station
  • the second base station is an LTE base station, and the UE type information includes at least the model of the UE, and may also include the software version number of the operating system of the UE.
  • the first base station is an NR base station
  • the second base station is an LTE base station
  • the first base station receives the first base station addition request sent by the second base station
  • the UE type information of the UE is carried in the first base station addition request Therefore, the first base station can perform differentiated management on the UE according to the UE type of the UE, so as to provide a better user experience. Since the UE type information of at least one UE is included in the first base station addition request, and the first base station addition request is a request for triggering the first base station to enter the dual-connection communication system of the UE, the first base station can provide communication for the UE.
  • the UE type information is obtained at the beginning of the service, which ensures that the UE can obtain good communication services after entering the dual-connection communication system; and the implementation of this solution is based on the existing network architecture, that is, it will not Great changes are made to the existing network architecture, and the feasibility of this solution is improved.
  • the request processing method provided in the embodiment of the present application may further include: terminal device management information may be pre-configured on the first base station, and the terminal device management information includes at least multiple UE types, and At least one feature corresponding to each UE type and a home list corresponding to each feature of each UE type one-to-one, after obtaining the UE type of the UE, the first base station can manage it according to the UE type and pre-configured terminal equipment
  • the information determines at least one characteristic of the UE, where the characteristic refers to a new technology introduced in the process of continuous improvement or change of the communication technology; and then the first base station can determine the attribution list corresponding to each characteristic in the at least one characteristic of the UE.
  • the first base station may combine at least one feature of the UE with each feature.
  • the home list corresponding to the feature manages the UE.
  • the first base station may determine at least one characteristic of the UE according to the UE type, and then perform differentiated management of the UE according to the at least one characteristic of the UE, because the characteristic refers to communication A new technology in the process of technological evolution or change.
  • Differentiate management of the UE based on at least one characteristic of the UE that is, determine the UE’s support for the characteristics of the first base station, so that the first base station determines which characteristics to perform on the UE to avoid This results in abnormal disconnection after the implementation of unsupported features for the UE, and improves the user's communication experience.
  • the terminal equipment management information may only include UE types with poor feature support, where the UE types with poor feature support means that the number of unsupported features reaches The UE type whose first threshold or the number of supported features is lower than the second threshold.
  • the multiple UE types included in the terminal equipment management information may only include UE types with poor feature support, that is, the first base station may only manage UE types with poor feature support, Reduce the workload of the first base station.
  • the attribution list of the terminal equipment management information may only include a blacklist and a graylist, where the blacklist refers to that the UE corresponding to the blacklist does not support the features corresponding to the blacklist,
  • the graylist refers to the operator's determination of whether the UE corresponding to the graylist supports the features corresponding to the graylist.
  • the attribution list of the terminal equipment management list since the UE generally supports most of the features of the first base station, the attribution list of the terminal equipment management list only includes the blacklist and graylist, which can not only reduce the storage occupied by the terminal equipment management list The space is also conducive to reducing the workload of the first base station for differentiated management of the UE.
  • the UE type information is carried in the International Mobile Equipment Identity soft version number Masked IMEISV cell, where the information carried by the Masked IMEISV cell can be divided into type assignment code, serial number and software version Specifically, the value of the 4-bit byte on the right side of the serial number is set to 1.
  • the cell carrying UE type information is determined to be the Masked IMEISV cell, which improves the practicability of this solution, and because the value of the right 4 bits of the SNR contained in the Masked IMEISV cell is set to 1. , Thereby avoiding the leakage of the true unique identification sequence number of the UE, and improving the security of the information transmission process; further, when the version of the operating system of the UE is different, the features supported by the UE may also be different, that is, the same model In addition, UEs with different operating system versions can be classified into different types of UEs.
  • the Masked IMEISV cell can include both the UE model and the operating system version number
  • the Masked IMEISV cell is used as the cell that carries the UE type information. , Can improve the accuracy of the first base station in determining the UE type.
  • the first base station addition request may carry multiple types of information, and the message structure of the first base station addition request may be pre-stored on the first base station.
  • the message structure includes at least the information name of each type of information and the appearance attribute of each type of information, where the appearance attribute of the UE type information of the UE is optional.
  • the appearance attribute of the UE type information is set to be optional, which improves the flexibility of the implementation of this solution, and because the first base station and the second base station store the UE type information in the message structure of the first base station addition request.
  • the presence attributes are all optional, and when the first base station receives the first base station addition request that does not contain UE type information, the normal operation of the first base station will not be affected, and the stability of the communication system is maintained.
  • the Masked IMEISV information element is obtained by the second base station from the initial context establishment request message sent by the mobility management entity; or, the Masked IMEISV information element is the second base station from the MME through the S1 interface Obtained from the first handover request message sent; or, the Masked IMEISV cell is obtained by the second base station from the second handover request message sent by the third base station through the X2 interface, and the third base station is the UE through handover access
  • an embodiment of the present application provides a request processing method.
  • the second base station may send a first base station addition request message to the first base station, when the first base station addition request message contains the UE type information of the terminal equipment UE
  • the first base station is a new air interface NR base station
  • the second base station is a long-term evolution LTE base station
  • the UE type information includes at least the model of the UE, and The software version number of the operating system of the UE may be included.
  • the message structure of the first base station addition request may be pre-stored on the second base station, and the message structure of the first base station addition request contains at least each type of information name and information related to each type.
  • the request processing method provided in the embodiment of the present application may further include: when the UE initially accesses the dual connectivity communication system, the second base station may receive the initial context establishment request sent by the mobility management entity Message, the initial context establishment request message carries the Masked IMEISV cell; or, when the UE switches into the dual-connection communication system through the S1 interface, the second base station receives the first handover request message sent by the mobility management entity through the S1 interface, and the first The handover request carries the Masked IMEISV cell; or, when the UE switches into the dual connectivity communication system through the X2 interface, the second base station receives the second handover request message sent by the third base station through the X2 interface, and the second handover request message carries There is a Masked IMEISV cell, the third base station is the LTE base station that the UE is connected to before accessing the dual connectivity communication system through handover, and the second base station is the LTE base station that is connected after the UE accesses
  • the second base station can also execute the steps described in the various possible implementation manners of the first aspect.
  • the various possible implementations please refer to the foregoing paragraph On the one hand, the various possible implementations are explained.
  • an embodiment of the present application is a base station.
  • the base station is a first base station, and the first base station includes a receiving unit and a processing unit.
  • the receiving unit is configured to receive the first base station addition request message sent by the second base station;
  • the processing unit is configured to determine the UE according to the first base station addition request message when the UE type information of the terminal equipment UE is included in the first base station addition request message
  • the first base station is a new air interface NR base station
  • the second base station is a long-term evolution LTE base station.
  • the component modules of the first base station can also execute the steps described in the various possible implementations of the first aspect.
  • the steps described in the various possible implementations of the first aspect please refer to the foregoing description of the first aspect and various possible implementations. instruction of.
  • the base station is a second base station.
  • the second base station includes a sending unit for sending a first base station addition request message to the first base station.
  • the first base station addition request message contains
  • the first base station add request message is used for the first base station to determine the type of the UE, where the first base station is a new air interface NR base station, and the second base station is a long-term evolution LTE base station.
  • the component modules of the second base station can also execute the steps described in the various possible implementations of the second aspect.
  • the steps described in the various possible implementations of the second aspect please refer to the foregoing description of the second aspect and various possible implementations. instruction of.
  • an embodiment of the present application provides a base station.
  • the base station is a first base station.
  • the first base station includes a receiver, a processor, and a memory, and the receiver is configured to receive a first base station addition request message sent by a second base station. And stored in the memory; the processor is used to determine the type of UE according to the first base station addition request message when the first base station addition request message contains the UE type information of the terminal equipment UE, where the first base station is a new air interface NR base station,
  • the second base station is a long-term evolution LTE base station.
  • the component modules of the first base station can also execute the steps described in the various possible implementations of the first aspect.
  • the steps described in the various possible implementations of the first aspect please refer to the foregoing description of the first aspect and various possible implementations. instruction of.
  • an embodiment of the present application provides a base station.
  • the base station is a second base station.
  • the second base station includes a transmitter and a processor.
  • the transmitter is configured to send a request to the first base station after the processor determines the first base station addition request.
  • the base station sends a first base station addition request message.
  • the first base station addition request message contains UE type information of the terminal equipment UE
  • the first base station addition request message is used for the first base station to determine the type of UE, where the first base station is The new air interface NR base station
  • the second base station is a long-term evolution LTE base station.
  • the component modules of the second base station can also perform the steps described in the various possible implementations of the second aspect.
  • the component modules of the second base station can also perform the steps described in the various possible implementations of the second aspect.
  • an embodiment of the present application provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, and when it runs on a computer or a processor, the computer or the processor executes the above The method of any one of the first aspect or the second aspect.
  • the embodiments of the present application provide a computer program product containing instructions that, when run on a computer or processor, cause the computer or processor to execute any one of the first or second aspects above The method described.
  • this application provides a chip system that includes a processor for supporting communication devices to implement the functions involved in the above aspects, for example, sending or processing data and/or information involved in the above methods .
  • the chip system further includes a memory, which is used to store program instructions and data necessary for the communication device.
  • the chip system may include chips or chips and other discrete devices.
  • the present application also provides a communication system.
  • the communication system includes a first base station and a second base station.
  • the first base station is used to implement the first aspect and the first base station in various possible implementation manners.
  • the second base station is used to execute the steps executed by the second base station in the foregoing second aspect and various possible implementation manners.
  • the present application also provides a communication system that includes a first base station, a second base station, and a third base station.
  • the first base station is used to implement the first aspect and various possible implementations.
  • the first base station performs the steps
  • the second base station is used to perform the above second aspect and the steps performed by the second base station in various possible implementation manners
  • the third base station is used to perform the above first or second aspects and each The steps performed by the third base station in one possible implementation manner.
  • FIG. 1 is a schematic structural diagram of a dual-connection communication system to which the request processing method provided in an embodiment of the application is applicable;
  • FIG. 2 is a schematic flowchart of a request processing method provided by an embodiment of the application
  • FIG. 3 is a schematic diagram of a structure of an international mobile equipment identification soft version number cell provided by an embodiment of this application;
  • FIG. 4 is a schematic flowchart of another request processing method provided by an embodiment of the application.
  • FIG. 5 is a schematic flowchart of another request processing method according to an embodiment of the application.
  • FIG. 6 is a schematic flowchart of still another request processing method according to an embodiment of the application.
  • FIG. 7 is a schematic structural diagram of a first base station provided by an embodiment of this application.
  • FIG. 8 is a schematic structural diagram of a second base station provided by an embodiment of this application.
  • FIG. 9 is a schematic diagram of another structure of a first base station provided by an embodiment of this application.
  • FIG. 10 is a schematic diagram of another structure of a second base station provided by an embodiment of this application.
  • the embodiments of the present application provide a request processing method, related device, and system.
  • the first base station can obtain UE type information of at least one UE from the first base station addition request sent by the second base station, and the second base station is provided to obtain the UE type. Information scheme.
  • the technical solutions of the embodiments of the present application can be applied to a dual connection scenario composed of at least two generations of communication systems.
  • the embodiments of the present application can be applied to a dual connection scenario composed of an LTE communication system and an NR communication system.
  • LTE communication system can include but not limited to LTE-A (LTE Advanced) system, or LTE-U system, or LTE authorized assisted access (LAA) system and NR system in dual connectivity scenarios.
  • LTE-NR dual connectivity e-utran nr dual connectivity, EN-DC
  • EN-DC dual connectivity e-utran nr dual connectivity, EN-DC
  • the embodiments of this application can also be applied to the dual-connection scenario formed by the NR communication system and the sixth-generation communication system, or in the dual-connection scenario formed by the sixth-generation communication system and the seventh-generation communication system, etc. Make a limit.
  • FIG. 1 shows a schematic diagram of a network architecture of an application environment of the request processing method provided by an embodiment of the present application, and a schematic diagram of a scenario where the technical solution provided by this application is applied to an EN-DC dual connection scenario .
  • the EN-DC dual-connection communication system includes at least one mobility management entity (MME), at least one LTE base station, and at least one NR base station.
  • MME mobility management entity
  • LTE base station at least one LTE base station
  • NR base station at least one NR base station.
  • the LTE base station refers to the base station in the LTE communication system, and can also be called the base station in the fourth-generation communication system or the evolved node B (eNB or eNodeB).
  • LTE base station can also be called master base station (MeNB);
  • NR base station refers to the base station in the NR communication system, and can also be called the base station or gNB in the fifth-generation communication system.
  • NR The base station may also be called a secondary base station (SgNB).
  • MME, LTE base station, and NR base station can be connected through communication interface.
  • MME and LTE base station can communicate through S1 interface; LTE base station and LTE base station can communicate through X2 interface; between MME and NR base station Communication can be carried out through the S1-U interface, and the S1-U interface is an optional interface; the communication interface between the LTE base station and the NR base station is also the X2 interface.
  • the current agreement stipulates that the MME can transmit the UE type information of the UE to the LTE base station through the S1 interface; different LTE base stations can transmit the UE type information through the X2 interface.
  • the terminal device involved in the embodiment of the present application may be a wireless terminal that provides voice and/or data connectivity to the user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem.
  • a wireless terminal can communicate with one or more core networks via a radio access network (RAN).
  • the wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal
  • RAN radio access network
  • the wireless terminal can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal
  • they can be portable, pocket-sized, handheld, computer-built or vehicle-mounted mobile devices, which exchange language and/or data with the wireless access network.
  • Wireless terminal can also be called system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, Remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), user equipment (user device), or user equipment (user equipment, UE), specifically not done here limited.
  • an embodiment of the present application proposes the following request processing method.
  • the specific implementation of the request processing method provided in this application will be described in detail below with reference to Figure 2.
  • Figure 2 is a possible embodiment of the request processing method provided in an embodiment of this application.
  • the method may include:
  • a first base station receives a first base station addition request message sent by a second base station.
  • the first base station is a base station in the M-th generation communication system
  • the second base station is a base station in the N-th generation communication system, where the value of M is greater than the value of N.
  • the first base station is an NR base station
  • the second base station is an LTE base station.
  • the first base station when a terminal device initially accesses the EN-DC dual-connection communication system, or when the terminal device moves from the LTE communication system to the EN-DC communication system, the first base station will send the first base station to the second base station.
  • Base station addition request message The first base station addition request is used to instruct the first base station to prepare and reserve radio resources for the UE to be accessed.
  • the first base station addition request may include the first base station addition trigger indication information, UE's security capability information and handover restriction list and other information.
  • the first base station addition request can be specifically expressed as a secondary base station addition request (SgNB addition request).
  • the first base station is the primary base station and the second base station is the secondary base station
  • the first base station addition request may also have other names, such as a primary base station addition request, etc., which are not specifically limited here.
  • both the first base station and the second base station can store the message structure of the first base station addition request.
  • the message structure of the request contains at least the name of each cell and the presence attribute corresponding to each cell.
  • the message structure of the first base station addition request may also contain a one-to-one correspondence with each cell. Specify the attribute of assigned criticality.
  • the appearance attribute is used to indicate the necessity of the cell corresponding to the appearance attribute in the first base station addition request.
  • the attribute value of the appearance attribute may be M, O or other attribute values, etc., M is required ( must).
  • M is required ( must).
  • M it means that the cell is a cell that must exist in the first base station's add request; O is the abbreviation for option.
  • the appearance attribute of the element is 0, it means that the cell is a cell that must exist in the first base station addition request; when the appearance attribute is other attribute values, it can also represent other meanings, and we will not list them one by one here. .
  • the first base station After the first base station receives the first base station addition request, it will parse the first base station addition request to obtain the multiple cells contained therein. Then, for a certain cell, either the analysis succeeds or the analysis fails.
  • the designated critical attribute is used to indicate the operation of the first base station when a certain cell analysis fails.
  • the attribute value of the designated critical attribute can be reject, ignore, or other attribute values, etc.
  • the first base station When the designated critical attribute value of a certain cell is rejected, when the first base station fails to analyze the cell, the first base station will perform the rejection operation, that is, the first base station will reject the message sent by the second base station.
  • the first base station adds a request; when the specified critical attribute value of a certain cell is ignored, then when the first base station fails to analyze the cell, the first base station will perform the ignore operation, that is, the first base station will not
  • the second base station feeds back, but continues to execute other procedures; when the designated critical attribute of the first cell is other attribute values, the second base station can also be instructed to perform other operations, which will not be listed here.
  • the first base station and the second base station may store the message structure of the first base station addition request by establishing a table, index or other types of methods.
  • the first base station and the second base station store the first base station in a table format.
  • the message structure of the base station addition request is taken as an example, which is described in detail in conjunction with Table 1 below.
  • Table 1 shows the description information of the four cells among the multiple cells included in the first base station addition request.
  • the name of the first cell is the information type, and the appearance attribute of the cell is
  • the attribute value of is M, that is, the first base station addition request must carry the information type of the first base station addition request, and the attribute value of the designated key attribute of the cell is reject, that is, when the first base station responds to the first base station When the information type of the add request fails to resolve, the first base station performs the rejection operation;
  • the name of the second cell is the security capability information of the UE in the NR system, and the attribute value of the appearance attribute of the above cell is M, specifying the critical attribute
  • the attribute value of is reject, that is, the security capability information of the UE in the NR system must be carried in the first base station addition request.
  • the rejection operation is performed; here
  • the third cell and the fourth cell will not be introduced in detail, but the combination of the third cell and the fourth cell shows that the attribute value of the appearance attribute of a certain cell and the attribute of the designated critical attribute
  • There is no fixed correspondence between the values that is, when the cell is an optional cell, the attribute value of the designated key attribute is ignored, and the determination of each attribute value is determined in accordance with the actual situation. It should be understood that the specific meaning of the four types of cells shown in Table 1 can be understood in conjunction with relevant protocols in the field.
  • the first base station may receive the first base station addition request message sent by the second base station through the X2 interface. After receiving the first base station addition request message, combined with the pre-stored message structure of the first base station addition request, The first base station addition request message is parsed to obtain the information carried by the first base station addition request message through multiple cells.
  • the first base station determines the type of the terminal device according to the first base station addition request message.
  • the UE type information of the UE includes at least the model information of the UE.
  • different brands of UE have different models, and different series of UE models of the same brand may also be different.
  • the type information of the UE may also include the software version number of the operating system of the UE.
  • the second base station may carry the model information of the UE in the international mobile station equipment identity and software version number (Masked IMEISV) cell, but It should be understood that in the third-generation communication system, the model information of the UE is carried in the international mobile station equipment identity (IMEI) cell, that is, in the future communication system, the model information of the UE can also be It is carried in other cells and is not limited here.
  • IMEI international mobile station equipment identity
  • the Masked IMEISV cell can be composed of 16-bit bytes, and the information composed of the 16-bit bytes can be divided into three parts, namely type allocation code (TAC). , Serial number (SNR) and software version number (software version number, SVN), the length of TAC is 8 bytes, which can be used to reflect the model of each UE; the length of SNR is 6 bytes, Used to uniquely identify a specific UE in a type of UE model, but in the Masked IMEISV cell, in order to prevent the base station from leaking the unique identification number of the UE, the value of the right 4-bit SNR is set to 1, thus avoiding information Security issues; the length of the SVN is 2 bytes, used to reflect the software version number of each UE's operating system.
  • TAC type allocation code
  • SNR Serial number
  • SVN software version number
  • the first base station addition request since the UE type information is added in the first base station addition request, the first base station addition request needs to extend new information elements to carry the UE type information.
  • the first base station and the second base station store The description information of the extended cell needs to be added to the message structure of the first base station addition request.
  • the description information of the extended cell includes at least the name of the extended cell and the appearance attribute of the extended cell, and may also include the designated key attribute of the extended cell. Specifically, with reference to Table 2 below, the case where the extended cell is a Masked IMEISV cell is described in detail.
  • Table 2 only shows the description information of the five cells included in the first base station addition request. Since the first four cells have been described in detail in conjunction with Table 1, they will not be repeated here. .
  • the appearance attribute of the Masked IMEISV cell is "O", that is, the appearance attribute of the Masked IMEISV cell is optional, that is, the Masked IMEISV may appear in the first base station addition request. Cells may not appear as Masked IMEISV cells.
  • the first base station can determine whether there is a Masked IMEISV cell in the first base station addition request. If there is a Masked IMEISV cell, then the first base station is parsed. The base station adds the request and obtains the UE type information carried therein; if there is no Masked IMEISV cell, only the other information contained in the first base station addition request is parsed and obtained, and the UE type information obtaining operation is not performed.
  • whether there is a Masked IMEISV cell in the first base station addition request can be further determined by the second base station in combination with other conditions.
  • the communication service provider may pre-set on the second base station Does the first base station add request include the Masked IMEISV information element; as another example, for example, since the UE type of the UE is used for the base station to determine at least one characteristic of the UE, the second base station may also determine the UE pair at least according to the UE type of the UE.
  • the second base station For the compatibility of one feature, only when the second base station determines that the UE has poor compatibility with at least one feature according to the UE type of the UE, the second base station sends the UE type information of the UE to the first base station; As another example, for example, the second base station also obtains the security level of the communication channel between the first base station and the second base station. When the security level of the communication channel between the first base station and the second base station is high, The first base station addition request sent by the first base station includes the Masked IMEISV information element; it should be understood that the first base station may further determine whether the first base station addition request includes the Masked IMEISV information element in combination with other situations.
  • the designated key attribute of the Masked IMEISV cell is ignored.
  • the first base station analyzes the first base station addition request, And obtain the UE type information carried therein, if the analysis fails in the analysis to obtain the UE type information, the first base station performs an ignore operation, that is, the information of the analysis failure is not fed back to the second base station.
  • the second base station since the designated critical attribute of the Masked IMEISV cell is ignored, even if the first base station addition request sent by the second base station to the first base station carries the Masked IMEISV cell, the second base station will also It cannot be assumed that the first base station has obtained the UE type information of the UE.
  • the first base station after the first base station receives the first base station addition request sent by the second base station, it can determine whether the first base station addition request includes UE type information of the UE.
  • the first base station addition request message includes UE
  • the first base station addition request may be parsed and the UE type information carried therein may be obtained, and then the first base station may determine the UE type according to the UE type information.
  • the first base station may determine the UE type according to the TAC in the Masked IMEISV cell, or the first base station may determine the UE’s type according to the TAC and SVN in the Masked IMEISV cell.
  • the cell carrying UE type information is determined to be a Masked IMEISV cell, which improves the practicability of this solution, and because the value of the right 4 bits of the SNR contained in the Masked IMEISV cell is set to 1, it is avoided
  • the true unique identification sequence number of the UE is leaked, which improves the security of the information transmission process; further, when the version of the operating system of the UE is different, the features supported by the UE may also be different, that is, the same model and operating system UEs with different versions can be classified into different types of UEs. Since the Masked IMEISV cell can include both the UE model and the operating system version number, the Masked IMEISV cell can be used as the cell carrying UE type information.
  • the accuracy of the first base station in determining the UE type is determined. It should be understood that when UE type information is carried in IMEI or other types of information elements, the type of UE can be determined in combination with other information contained in other types of information elements, which is not limited here.
  • the first base station determines at least one characteristic of the terminal device according to the terminal device type of the terminal device.
  • the first base station may be pre-configured with terminal device management information.
  • the first base station may store the aforementioned terminal device management information in a table, index, array or other form.
  • the terminal equipment management information includes at least the UE type and characteristics, and the terminal equipment management information includes multiple UE types, and each UE type corresponds to at least one characteristic.
  • the characteristic refers to the new technology introduced in the process of continuous improvement or change of the communication technology, as examples, such as: power saving mode, continuous reception (discontinuous reception, DRX), carrier aggregation (CA) and/or physical Cell identity (physical cell identity, PCI) conflict detection, etc.
  • power saving mode continuous reception
  • DRX discontinuous reception
  • CA carrier aggregation
  • PCI physical Cell identity
  • the terminal equipment management information preset by the first base station may also include a one-to-one correspondence with each feature of each UE type.
  • the home list is used to indicate whether the UE corresponding to the home list supports the feature corresponding to the home list, that is, when the UE corresponding to the home list executes the feature corresponding to the home list, whether the UE will operate abnormally.
  • the attribution list may include a white list, a black list, and a gray list, where the white list refers to that the UE corresponding to the white list supports features corresponding to the white list, and the black list refers to that the UE corresponding to the black list does not support The feature corresponding to the blacklist.
  • the graylist refers to the operator's determination of whether the UE corresponding to the graylist supports the feature corresponding to the graylist. Below, only the first base station stores the aforementioned terminal device management information in the form of a terminal device management list As an example, it will be described in detail in conjunction with Table 3.
  • Type of terminal equipment characteristic Attribution list Type 1 Power saving mode blacklist
  • Type 1 Discontinuous reception blacklist Type 2 Power saving mode whitelist
  • Type 2 Carrier aggregation whitelist Type 3 Physical cell identity conflict detection Greylist
  • Type 3 Discontinuous reception whitelist Type 4 Discontinuous reception Greylist
  • Table 3 only shows part of the content of the terminal equipment management list stored by the first base station, including 4 types of terminal equipment. Among them, there are two characteristics corresponding to the type 1 UE, namely the power saving mode. And discontinuous reception, the attribution lists corresponding to the power saving mode and discontinuous reception of type 1 UE are all blacklists, that is, the type 1 UE does not support power saving mode or discontinuous reception; The UE has two characteristics corresponding to the power saving mode and carrier aggregation. The home list corresponding to the power saving mode and carrier aggregation of the type 1 UE is whitelisted, that is, the type 2 UE supports both the power saving mode and the carrier aggregation.
  • the home list corresponding to the physical cell identity conflict detection of type 3 UEs is graylist, that is, type 3. Whether the UE supports physical cell identity conflict detection needs to be further determined by the operator.
  • the home list corresponding to the discontinuous reception of the type 3 UE is a whitelist, that is, the type 3 UE supports discontinuous reception, and the type 4 is no longer
  • the examples in Table 3 are only to facilitate the understanding of this solution.
  • the specific features supported by different types of UEs and the determination of the home list should be flexibly determined in combination with the actual situation of the UE, which is not limited here.
  • the attribution list in the terminal equipment management list may only include blacklists and graylists, that is, in addition to determining which types of UEs do not support which features in the terminal equipment management list, for other features on the first base station, you can All are supported by default.
  • Blacklists and graylists that is, in addition to determining which types of UEs do not support which features in the terminal equipment management list, for other features on the first base station, you can All are supported by default.
  • Table 3 as an example, that is, the data in the fourth row, fifth row, and seventh row in Table 3 does not exist in the terminal device management list.
  • the UE supports most of the features of the first base station, and the attribution list of the terminal equipment management list only includes blacklist and graylist, which not only reduces the storage space occupied by the terminal equipment management list, but also helps Reduce the workload of the first base station for differentiated management of the UE.
  • the multiple UE types included in the terminal equipment management information may only include UE types with poor feature support, that is, UE types with fewer features supported. Specifically, it may be a certain type of UE.
  • UE types with poor feature support that is, UE types with fewer features supported.
  • it may be a certain type of UE.
  • the UE type is regarded as having poor support for the feature UE type.
  • the terminal device management list only includes UE types with poor feature support.
  • the first base station can match the terminal management list according to the UE type of the UE. If the terminal equipment management list does not exist For the UE type, all features on the first base station can be regarded as at least one feature corresponding to the UE, and can be regarded as the UE supporting all features on the first base station; if all features on the terminal device management list exist.
  • the UE type, at least one characteristic corresponding to the UE type recorded in the terminal equipment management list is determined as at least one characteristic of the UE, and each characteristic of the at least one characteristic is determined according to the terminal equipment management list Is the attribution list whitelisted or blacklisted or graylisted?
  • the first base station can match the UE type of the UE with the terminal management list. If the UE type does not exist in the home list, Then all the characteristics on the first base station can be regarded as at least one characteristic corresponding to the UE, and can be regarded as the UE supporting all the characteristics on the first base station; if the UE type exists in the terminal equipment management list, then Determine at least one characteristic corresponding to the UE type recorded in the terminal equipment management list as at least one characteristic of the UE, and determine according to the terminal equipment management list that the home list of each characteristic in the at least one characteristic is black
  • the list is also a gray list, and features other than the at least one feature on the first base station are regarded as features supported by the UE.
  • the multiple UE types included in the terminal equipment management information may only include UE types with poor feature support, that is, the first base station may only manage the UE types with poor feature support.
  • the UE type reduces the workload of the first base station.
  • the first base station can determine the UE type of the UE according to the UE’s
  • the UE type queries the terminal management list to determine at least one characteristic corresponding to the UE, and whether the home list corresponding to each characteristic of the UE is a whitelist, a blacklist or a graylist.
  • Each UE of each type of UE and each characteristic of each type of UE has a corresponding record in the terminal management list, which improves the rigor of the first base station in the UE management process.
  • the terminal equipment management list does not include all UE types, and the attribution list only includes blacklists. The situation of list and grey list is discussed.
  • the first base station manages the terminal device according to at least one characteristic of the terminal device.
  • the first base station can obtain at least one characteristic of the UE through step 203, and determine the attribution list corresponding to each characteristic of the at least one characteristic of the UE, that is, it can obtain whether the UE supports all characteristics. Describe each of at least one characteristic. Specifically, the first base station can directly execute the feature whose home list is a whitelist or the feature supported by the UE; for the feature whose home list is a blacklist, the first base station can prohibit activation; for the feature whose home list is a graylist, A base station may not be activated temporarily, and the operator may further determine whether the UE supports the feature.
  • the first base station can determine at least one characteristic of the UE according to the UE type, and then perform differentiated management of the UE according to the at least one characteristic of the UE.
  • the characteristic refers to the evolution or change process of the communication technology.
  • the UE performs differentiated management based on at least one characteristic of the UE, that is, it determines the UE’s support for the characteristics of the first base station, so that the first base station determines which characteristics to perform on the UE, so as to avoid causing the UE to perform Circumstances such as abnormal disconnection after the unsupported feature improves the user's communication experience.
  • the first base station does not obtain the terminal equipment type information.
  • step 202 to step 204 and step 205 cannot exist at the same time.
  • the first base station when the first base station is an NR base station and the second base station is an LTE base station, the first base station receives the first base station addition request sent by the second base station, and the UE type of the UE is carried in the first base station addition request
  • the first base station can perform differentiated management on the UE according to the UE type of the UE, so as to provide a better user experience. Since the UE type information of at least one UE is included in the first base station addition request, and the first base station addition request is a request for triggering the first base station to enter the dual-connection communication system of the UE, the first base station can provide communication for the UE.
  • the UE type information is obtained at the beginning of the service, which ensures that the UE can obtain good communication services after entering the dual-connection communication system; and the implementation of this solution is based on the existing network architecture, that is, it will not Great changes are made to the existing network architecture, and the feasibility of this solution is improved.
  • the application of the embodiments of the present application in an EN-DC dual-connection communication system is taken as an example for specific description.
  • the terminal device can be further divided.
  • the terminal device can be initially connected to the EN-DC dual-connection communication system, or it can be switched into the terminal device through the S1 interface.
  • the EN-DC dual-connection communication system can also switch the terminal device into the EN-DC dual-connection communication system through the X2 interface. Because the specific execution steps in the foregoing three scenarios are different, the following are examples combining the foregoing three application scenarios. .
  • FIG. 4 is a possible embodiment of the request processing method provided by the embodiments of the present application.
  • the method may include:
  • the mobility management entity sends an initial context establishment request message to the LTE base station.
  • the MME may select an LTE base station (that is, the second base station) for the UE, and send an initial context establishment request (initial context establishment request) to the LTE base station. setup request) message, the initial context setup request message contains the Masked IMEISV information element used to carry UE type information, so that the LTE base station can obtain the Masked IMEISV information element from the initial context setup request message to obtain the UE’s UE type information.
  • the LTE base station sends an initial context establishment complete message to the mobility management entity.
  • the LTE base station after receiving the initial context establishment request message sent by the MME, the LTE base station can interact with the terminal equipment to obtain the capability information of the UE, order the UE to turn on the security mode (security mode), and The radio resource control (RRC) reconfiguration (RRC Conn reconfiguration) message can be sent to the UE so that the terminal device can obtain the configuration information of the radio resource on the LTE base station.
  • RRC radio resource control
  • the LTE base station sends a secondary base station addition request message to the NR base station.
  • the LTE base station after the LTE base station completes the establishment of the initial context, it can send a secondary base station addition request (SgNB addition request) message to the NR base station through the X2 interface between the LTE base station and the NR base station (that is, the first base station). Then the secondary base station addition request message may extend the Masked IMEISV information element to send the UE type information of the UE to the NR base station.
  • the secondary base station addition request message is the first base station addition request in the embodiment described in FIG. 2, and the secondary base station addition request may also include other information. What information is included in the base station addition request can be understood in conjunction with the description in the embodiment of FIG. 2 and related protocols in the field, and will not be described in detail here.
  • the NR base station sends a secondary base station addition request response message to the LTE base station.
  • the NR base station after receiving the secondary base station addition request message, the NR base station adds a request response (SgNB addition request acknowledge) message to the secondary base station corresponding to the LTE base station, and the secondary base station addition request response message contains the NR The configuration information of the wireless resource of the base station.
  • SgNB addition request acknowledge a request response (SgNB addition request acknowledge) message
  • the LTE base station sends an RRC reconfiguration message to the terminal device.
  • the LTE base station after receiving the secondary base station addition request response message sent by the NR base station, the LTE base station can send an RRC reconfiguration message (RRC Conn reconfiguration) to the terminal device again, so that the terminal device can obtain the data bearer on the NR base station According to the configuration information of the LTE base station and the NR base station, the terminal device can perform an access operation according to the configuration information of the radio resources on the LTE base station and the NR base station.
  • RRC reconfiguration message RRC Conn reconfiguration
  • FIG. 5 is a possible embodiment of the request processing method provided by the embodiments of the present application.
  • the method may include:
  • the mobility management entity sends a handover request message to a target LTE base station.
  • the target LTE base station is the LTE base station (that is, the second base station) connected after the terminal device performs a handover access operation.
  • the MME can send a handover request message (that is, the first handover request message) to the target LTE base station through the S1 interface, which is used to request the target LTE base station to prepare for the UE that accesses the EN-DC dual-connection communication system through handover. Reserve the required resources.
  • the first handover request message contains the Masked IMEISV information element for carrying UE type information, so that the target LTE base station can obtain the Masked IMEISV information element from the first handover request message to obtain the UE of the UE. Type information.
  • the target LTE base station sends a handover request confirmation message to the mobility management entity.
  • the target LTE base station determines whether to allow access after receiving the handover request message, and sends a handover request acknowledgement message to the MME when the access is allowed, so that the MME cooperates with the source LTE base station to release the source
  • the target LTE base station can receive the RRC configuration complete (RRC Conn reconfiguration complete) message, and proceed to step 503, where ,
  • the source LTE base station is the LTE base station connected before the terminal device performs the handover access operation.
  • the target LTE base station sends a secondary base station addition request message to the NR base station.
  • the NR base station sends a secondary base station addition request response message to the target LTE base station.
  • the target LTE base station sends an RRC reconfiguration message to the terminal device.
  • steps 503 to 505 are similar to steps 403 to 405 in the embodiment described in FIG. 4, except that steps 403 to 405 are information exchange between the LTE base station and the NR base station during initial access.
  • steps 503 to 505 the target LTE base station connected to the NR base station after the terminal device performs the handover access operation performs information exchange, which is not repeated here.
  • FIG. 6, is a possible embodiment of the request processing method provided in the embodiments of the present application.
  • the method may include:
  • the source LTE base station sends a handover request message to the target LTE base station.
  • the source LTE base station (that is, the third base station) is the LTE base station connected before the terminal device performs the handover access operation
  • the target LTE base station (that is, the second base station) is the terminal device connected after the handover access operation is performed.
  • the source LTE base station can directly send the handover request message (that is, the second handover request message) to the target LTE base station through the X2 interface, so that the target LTE base station can obtain the UE from the Masked IMEISV cell in the second handover request message
  • the content contained in the second handover request message is similar to the content contained in the first handover request message in step 501, and will not be repeated here.
  • the target LTE base station sends a secondary base station addition request message to the NR base station.
  • the NR base station sends a secondary base station addition request response message to the LTE base station.
  • step 602 and step 603 are similar to step 503 and step 504 in the embodiment described in FIG. 5, and will not be repeated here.
  • the target LTE base station sends a handover request response message to the source LTE base station.
  • the target LTE base station after the target LTE base station receives the secondary base station addition request response message sent by the NR base station (that is, the first base station), it can send a handover request response message to the source LTE base station to trigger the source LTE base station to perform radio resource release , Bearer data forwarding and other operations, and after the execution is completed, the target LTE base station can notify the MME to perform path switching.
  • the above is combined with the terminal device to initially access the EN-DC dual-connection communication system, the terminal device switches into the EN-DC dual-connection communication system through the S1 interface, and the terminal device switches into the EN-DC dual-connection communication through the X2 interface.
  • the three scenarios of the system introduce in detail the specific implementation of the request processing method provided by the embodiment of this application, expand the application scenarios of this solution, and also enhance the executability of this solution.
  • FIG. 7 is a schematic structural diagram of a first base station according to an embodiment of the application.
  • the first base station 700 includes a receiving unit 701 and a processing unit 702.
  • the receiving unit 701 is configured to receive the first base station addition request message sent by the second base station;
  • the processing unit 702 is configured to, when the first base station addition request message contains UE type information of the terminal equipment UE, the first base station
  • the add request message determines the type of UE, where the first base station is a new air interface NR base station, and the second base station is a long-term evolution LTE base station.
  • the first base station is an NR base station
  • the second base station is an LTE base station.
  • the receiving unit 701 receives the first base station addition request sent by the second base station.
  • the first base station addition request carries the UE type information of the UE.
  • the processing unit 702 may perform differentiated management on the UE according to the UE type of the UE, so as to provide a better user experience. Since the UE type information of at least one UE is included in the first base station addition request, and the first base station addition request is a request for triggering the first base station to enter the dual-connection communication system of the UE, the first base station can provide communication for the UE.
  • the UE type information is obtained at the beginning of the service, which ensures that the UE can obtain good communication services after entering the dual-connection communication system; and the implementation of this solution is based on the existing network architecture, that is, it will not Great changes are made to the existing network architecture, and the feasibility of this solution is improved.
  • the processing unit 702 is further configured to determine at least one characteristic of the UE according to the UE type of the UE, and to manage the UE according to the at least one characteristic of the UE.
  • the UE type information is carried in the Masked IMEISV cell.
  • the message structure of the first base station addition request is pre-stored on the first base station, and the message structure of the first base station addition request contains at least the information name of each type of information and the information of each type of information. Presence attribute, where the presence attribute of UE type information is optional.
  • the masked IMEISV information element is obtained by the second base station from the initial context establishment request message sent by the mobility management entity MME; or, the masked IMEISV information element is the first handover sent by the second base station from the MME Obtained in the request message; or, the Masked IMEISV information element is obtained by the second base station from the second handover request message sent by the third base station, and the third base station is an LTE base station.
  • the first base station 700 provided by the embodiment of the present application is used to execute the method executed by the first base station in the method embodiments corresponding to FIG. 2 to FIG. 6. Therefore, for the embodiment of the present application, refer to the method embodiments corresponding to FIG. 2 to FIG. To understand the relevant parts, I won’t repeat them here.
  • the second base station 800 includes a sending unit 801.
  • the sending unit 801 is configured to send a first base station addition request message to the first base station.
  • the first base station addition request message contains UE type information of the terminal equipment UE
  • the first base station addition request message is used for the first base station to determine the UE
  • the first base station is a new air interface NR base station
  • the second base station is a long-term evolution LTE base station.
  • the UE type information is carried in the Masked IMEISV cell.
  • the message structure of the first base station addition request is pre-stored on the second base station, and the message structure of the first base station addition request contains at least the name of each type of information and the appearance of each type of information. (presence) attribute, where the presence attribute of the UE type information of the UE is optional.
  • the second base station 800 further includes a receiving unit 802, specifically configured to: receive an initial context establishment request message sent by the mobility management entity MME, where the initial context establishment request message carries a Masked IMEISV information element; or, Receive the first handover request message sent by the mobility management entity MME, the first handover request carries the Masked IMEISV information element; or, receive the second handover request message sent by the third base station, the second handover request message carries the Masked IMEISV information Yuan, the third base station is an LTE base station.
  • the second base station 800 provided by the embodiment of the present application is used to execute the method executed by the second base station in the method embodiments corresponding to FIG. 2 to FIG. 6. Therefore, for the embodiment of the present application, refer to the method embodiments corresponding to FIG. 2 to FIG. To understand the relevant parts, I won’t repeat them here.
  • FIG. 9 is a schematic structural diagram of a first base station provided by an embodiment of the present application.
  • the first base station 900 includes: a receiver 901 and a transmitter 902 , A processor 903 and a memory 904 (the number of processors 903 in the first base station 900 may be one or more, and one processor is taken as an example in FIG. 9), where the processor 903 may include an application processor 9031 and a communication Processor 9032.
  • the receiver 901, the transmitter 902, the processor 903, and the memory 904 may be connected by a bus or other methods.
  • the memory 904 may include a read-only memory and a random access memory, and provides instructions and data to the processor 903. A part of the memory 904 may also include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 904 stores a processor and operating instructions, executable modules or data structures, or a subset of them, or an extended set of them, where the operating instructions may include various operating instructions for implementing various operations.
  • the processor 903 controls the operation of the terminal device.
  • the various components of the terminal device are coupled together through a bus system.
  • the bus system may also include a power bus, a control bus, and a status signal bus.
  • various buses are referred to as bus systems in the figure.
  • the method disclosed in the foregoing embodiment of the present application may be applied to the processor 903 or implemented by the processor 903.
  • the processor 903 may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method can be completed by an integrated logic circuit of hardware in the processor 903 or instructions in the form of software.
  • the above-mentioned processor 903 may be a general-purpose processor, a digital signal processing (DSP), a microprocessor or a microcontroller, and may further include an application specific integrated circuit (ASIC), field programmable Field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processing
  • ASIC application specific integrated circuit
  • FPGA field programmable Field-programmable gate array
  • the processor 903 can implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory 904, and the processor 903 reads the information in the memory 904, and completes the steps of the foregoing method in combination with its hardware.
  • the receiver 901 can be used to receive input digital or character information, and to generate signal input related to the relevant settings and function control of the terminal device.
  • the transmitter 902 can be used to output digital or character information through the first interface; the transmitter 902 can also be used to send instructions to the disk group through the first interface to modify the data in the disk group; the transmitter 902 can also include display devices such as a display screen .
  • the first base station 900 is used to execute the request processing method executed by the aforementioned first base station.
  • the receiver 901 receives the first base station addition request message sent by the second base station.
  • the processor 903 determines the UE’s status according to the first base station addition request message.
  • Type where the first base station is a new air interface NR base station, and the second base station is a long-term evolution LTE base station.
  • the first base station is an NR base station
  • the second base station is an LTE base station
  • the receiver 901 receives the first base station addition request sent by the second base station.
  • the first base station addition request carries the UE type information of the UE.
  • the processor 903 may perform differentiated management on the UE according to the UE type of the UE, so as to provide a better user experience. Since the UE type information of at least one UE is included in the first base station addition request, and the first base station addition request is a request for triggering the first base station to enter the dual-connection communication system of the UE, the first base station can provide communication for the UE.
  • the UE type information is obtained at the beginning of the service, which ensures that the UE can obtain good communication services after entering the dual-connection communication system; and the implementation of this solution is based on the existing network architecture, that is, it will not Great changes are made to the existing network architecture, and the feasibility of this solution is improved.
  • the processor 903 is further configured to determine at least one characteristic of the UE according to the UE type of the UE, and to manage the UE according to the at least one characteristic of the UE.
  • the UE type information is carried in the Masked IMEISV cell.
  • the message structure of the first base station addition request is pre-stored in the memory 904, and the message structure of the first base station addition request contains at least the information name of each type of information and the appearance of each type of information. (presence) attribute, where the presence attribute of UE type information is optional.
  • the masked IMEISV information element is obtained by the second base station from the initial context establishment request message sent by the mobility management entity MME; or, the masked IMEISV information element is the first handover sent by the second base station from the MME Obtained in the request message; or, the Masked IMEISV information element is obtained by the second base station from the second handover request message sent by the third base station, and the third base station is an LTE base station.
  • the first base station 900 provided in the embodiment of the present application is used to execute the method executed by the first base station in the method embodiments corresponding to FIG. 2 to FIG. 6. Therefore, in the embodiment of the present application, refer to the method embodiments corresponding to FIG. 2 to FIG. To understand the relevant parts, I won’t repeat them here.
  • the second base station 1000 includes: a receiver 1001, a transmitter 1002, a processor 1003, and a memory 1004 (the processing in the second base station 1000
  • the number of the processor 1003 may be one or more.
  • one processor is taken as an example), where the processor 1003 may include an application processor 10031 and a communication processor 10032.
  • the receiver 1001, the transmitter 1002, the processor 1003, and the memory 1004 may be connected by a bus or other means.
  • the memory 1004 may include a read-only memory and a random access memory, and provides instructions and data to the processor 1003. A part of the memory 1004 may also include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1004 stores a processor and operating instructions, executable modules or data structures, or a subset of them, or an extended set of them, where the operating instructions may include various operating instructions for implementing various operations.
  • the processor 1003 controls the operation of the terminal device.
  • the various components of the terminal device are coupled together through a bus system.
  • the bus system may also include a power bus, a control bus, and a status signal bus.
  • various buses are referred to as bus systems in the figure.
  • the methods disclosed in the foregoing embodiments of the present application may be applied to the processor 1003 or implemented by the processor 1003.
  • the processor 1003 may be an integrated circuit chip with signal processing capability. In the implementation process, the steps of the foregoing method can be completed by an integrated logic circuit of hardware in the processor 1003 or instructions in the form of software.
  • the aforementioned processor 1003 may be a general-purpose processor, a digital signal processing (DSP), a microprocessor or a microcontroller, and may further include an application specific integrated circuit (ASIC), field programmable Field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processing
  • ASIC application specific integrated circuit
  • FPGA field programmable Field-programmable gate array
  • the processor 1003 can implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory 1004, and the processor 1003 reads information in the memory 1004, and completes the steps of the foregoing method in combination with its hardware.
  • the receiver 1001 can be used to receive input digital or character information, and to generate signal input related to the relevant settings and function control of the terminal device.
  • the transmitter 1002 can be used to output digital or character information through the first interface; the transmitter 1002 can also be used to send instructions to the disk group through the first interface to modify the data in the disk group; the transmitter 1002 can also include display devices such as a display .
  • the second base station 1000 is used to execute the request processing method executed by the aforementioned second base station.
  • the transmitter 1002 is configured to, after the processor 1003 determines the first base station addition request, send a first base station addition request message to the first base station, and when the first base station addition request message contains UE type information of the terminal equipment UE, The first base station addition request message is used for the first base station to determine the type of UE, where the first base station is a new air interface NR base station, and the second base station is a long-term evolution LTE base station.
  • the UE type information is carried in the Masked IMEISV cell.
  • the message structure of the first base station addition request is pre-stored on the second base station, and the message structure of the first base station addition request contains at least the name of each type of information and the appearance of each type of information. (presence) attribute, where the presence attribute of the UE type information of the UE is optional.
  • the receiver 1001 is used to: receive the initial context establishment request message sent by the mobility management entity MME, and the initial context establishment request message carries the Masked IMEISV information element; or, receive the initial context establishment request message sent by the mobility management entity MME.
  • the first handover request message the first handover request carries the Masked IMEISV cell; or the second handover request message sent by the third base station is received, the second handover request message carries the Masked IMEISV cell, and the third base station is LTE Base station.
  • the embodiment of the present application also provides a computer program product including a request processing instruction, which when running on a computer, causes the computer to execute the method performed by the first base station in the method described in the embodiments shown in FIGS. 2 to 6 step.
  • the embodiment of the present application also provides a computer program product including a request processing instruction, which when it runs on a computer, causes the computer to execute the method performed by the second base station in the method described in the embodiments shown in FIG. 2 to FIG. step.
  • the embodiments of the present application also provide a computer-readable storage medium that stores instructions for transferring between communication systems. When it runs on a computer, the computer executes the instructions shown in FIGS. 2 to 6 above. The steps performed by the first base station in the method described in the embodiment are shown.
  • the embodiments of the present application also provide a computer-readable storage medium that stores instructions for transferring between communication systems. When it runs on a computer, the computer executes the instructions shown in FIGS. 2 to 6 above. The steps performed by the second base station in the method described in the embodiment are shown.
  • An embodiment of the present application also provides a communication system.
  • the communication system includes a first base station and a second base station.
  • the first base station is the first base station described in the embodiment shown in FIG. 7 or the foregoing FIG. 9, and the second base station is The second base station described in the embodiment shown in the foregoing FIG. 8 or the foregoing FIG. 10.
  • An embodiment of the present application also provides a communication system.
  • the communication system includes a first base station, a second base station, and a third base station.
  • the first base station executes the first of the methods described in the embodiments shown in FIGS. 2 to 6 above.
  • the steps performed by the base station, the second base station performs the steps performed by the second base station in the method described in the embodiments shown in FIGS. 2 to 6, and the third base station performs the steps described in the embodiments shown in FIGS. 2 to 6
  • the device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physically separate
  • the physical unit can be located in one place or distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the connection relationship between the modules indicates that they have a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.
  • this application can be implemented by means of software plus necessary general hardware.
  • it can also be implemented by dedicated hardware including dedicated integrated circuits, dedicated CPUs, dedicated memory, Dedicated components and so on to achieve.
  • all functions completed by computer programs can be easily implemented with corresponding hardware.
  • the specific hardware structure used to achieve the same function can also be diverse, such as analog circuits, digital circuits or dedicated Circuit etc.
  • software program implementation is a better implementation in more cases.
  • the technical solution of this application essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, such as a computer floppy disk.
  • a readable storage medium such as a computer floppy disk.
  • U disk transfer hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk, etc., including several instructions to make a computer device (which can be A personal computer, server, or network device, etc.) execute the method described in each embodiment of the present application.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种请求处理方法、相关装置及系统，第一基站可以从第二基站发送的第一基站添加请求中获取至少一个UE的UE类型信息，提供了第二基站获取UE类型信息的方案。方法包括：第一基站接收第二基站发送的第一基站添加请求消息；当第一基站添加请求消息中包含终端设备UE的UE类型信息时，第一基站根据第一基站添加请求消息确定UE的类型；其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站。

Description

一种请求处理方法、相关装置及系统
本申请要求于2019年3月28日提交中国专利局、申请号为201910243889.9、发明名称为“一种请求处理方法、相关装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种请求处理方法、相关装置及系统。
背景技术
无线通信系统中不断有新的特性被推出，而终端设备的品牌和型号也越来越多，不同类型的终端支持的特性可能不同，也即不是无线通信系统推出的所有特性都能被所有类型的终端支持。当基站使用的特性不被终端设备支持时，容易出现异常掉话的现象，降低了系统性能。
在长期演进(long term evolution，LTE)系统中，3GPP协议中定义了移动管理实体(mobility management entity，MME)与演进型基站(evolutional node B，eNB或eNodeB)之间UE类型信息的传递流程，也定义了eNB与eNB之间终端设备的类型信息的传递流程，从而可以方便eNB对不同类型的终端设备进行差异化管理。
但无线通信系统开始演进为第五代(5th generation，5G)无线通信系统，终端设备通过LTE系统与NR系统所构成的双连接(dual connection，DC)通信系统进行数据传输，但目前协议中却没有关于新空口(new radio，NR)系统中的基站(gNB)如何获取到终端设备(user equipment，UE)的类型信息的定义，因此，一套能够帮助gNB获取到终端设备的类型信息的方案亟待推出。
发明内容
本申请实施例提供了一种请求处理方法、相关装置及系统，第一基站可以从第二基站发送的第一基站添加请求中获取至少一个UE的UE类型信息，提供了第二基站获取UE类型信息的方案。
第一方面，本申请实施例提供一种请求处理方法。
在UE进入LTE通信系统和NR通信系统构成的双连接通信系统之后，第一基站可以接收第二基站发送的第一基站添加请求消息，第一基站添加请求用于指示第一基站为即将接入的UE准备无线资源，当第一基站添加请求消息中包含UE的UE类型信息时，第一基站根据第一基站添加请求消息中的UE类型信息确定UE的类型，其中，第一基站为NR基站，第二基站为LTE基站，UE类型信息中至少包含UE的型号，还可以包含UE的操作系统的软件版本号。
在本申请中，第一基站为NR基站，第二基站为LTE基站，第一基站接收到第二基站发送的第一基站添加请求，在第一基站添加请求中携带UE的UE类型信息的情况下，从而第一基站可以根据UE的UE类型对UE进行差异化管理，以提供更良好的用户体验。由于 至少一个UE的UE类型信息是包含在第一基站添加请求中的，而第一基站添加请求是触发第一基站进入UE的双连接通信系统的请求，从而第一基站可以在为UE提供通信服务的初始即获取到UE的类型信息，则保证了UE从进入双连接通信系统之后即可以获取到良好的通信服务；且本方案的实施是基于现有的网络架构实现的，也即不会给现有的网络架构造成很大的改变，提高了本方案的可实现性。
在第一方面的一种可能实现中，本申请实施例提供的请求处理方法还可以包括：第一基站上可以预先配置有终端设备管理信息，终端设备管理信息中至少包括多种UE类型、与每种UE类型对应的至少一个特性以及与每种UE类型的每个特性一一对应的归属名单，则第一基站在获取到UE的UE类型之后，可以根据UE类型以及预先配置的终端设备管理信息确定UE的至少一个特性，其中，特性指的是通信技术在不断改进或改变过程中引入的新技术；进而第一基站可以确定UE的至少一个特性中每个特性对应的归属名单，归属名单用于指示与归属名单对应的UE对与归属名单对应的特性的支持情况，第一基站在确定UE的至少一个特性中每个特性对应的归属名单之后，可以结合UE的至少一个特性和每个特性对应的归属名单对UE进行管理。
在本申请中，第一基站在获取到UE的UE类型之后，可以根据UE类型确定UE的至少一个特性，并进而根据UE的至少一个特性对UE进行差异化管理，由于特性指的是在通信技术演进或改变过程中的新技术，根据UE的至少一个特性对UE进行差异化管理，也即确定UE对第一基站上的特性的支持情况，从而第一基站确定对UE执行哪些特性，避免导致对UE执行了不支持的特性之后出现的异常掉线等情况，提高用户的通信体验。
在第一方面的一种可能实现中，终端设备管理信息可以仅包含对特性的支持性较差的UE类型，其中，对特性的支持性较差的UE类型指的是不支持的特性数量达到第一阈值或者支持的特性数量低于第二阈值的UE类型。
在本申请中，终端设备管理信息中包含的多种UE类型中可以仅包含对特性的支持性较差的UE类型，也即第一基站可以仅管理对特性的支持性较差的UE类型，减少了第一基站的工作负荷。
在第一方面的一种可能实现中，终端设备管理信息的归属名单中可以仅包含黑名单和灰名单，其中，黑名单指的是与黑名单对应的UE不支持与黑名单对应的特性，灰名单指的是由运营商确定与灰名单对应的UE是否支持与灰名单对应的特性。
在本申请中，由于一般情况下，UE对第一基站的大部分特性都是支持的，终端设备管理列表的归属名单中仅包含黑名单和灰名单，不仅可以减少终端设备管理列表占用的存储空间，也有利于降低第一基站对UE进行差异化管理的工作负荷。
在第一方面的一种可能实现中，UE类型信息携带于国际移动设备标识软版号Masked IMEISV信元中，其中，Masked IMEISV信元携带的信息可以分为类型分配码、序列号和软件版本号，具体的，序列号的右边4位字节的值均置1。
在本申请中，将携带UE类型信息的信元确定为Masked IMEISV信元，提高了本方案的可执行性，且由于Masked IMEISV信元中包含的SNR的右边4位字节的值均置1，从而避免了UE的真实的唯一标识序列号被泄露，提高了信息传输过程的安全性；进一步的，当UE的操作系统的版本不同时，UE支持的特性也可能会不同，也即同一型号且操作系统 版本不同的UE可以被划分为不同类型的UE，由于Masked IMEISV信元中可以同时包括UE的型号以及操作系统的版本号，则采用Masked IMEISV信元作为携带UE类型信息的信元时，可以提高第一基站在确定UE类型过程中的精度。
在第一方面的一种可能实现中，第一基站添加请求中可以携带有多种类型的信息，则第一基站上可以预先存储有第一基站添加请求的消息结构，第一基站添加请求的消息结构中至少包含每种类型的信息的信息名称以及每种类型的信息的出现属性，其中，UE的UE类型信息的出现属性为可选。
在本申请中，将UE类型信息的出现属性设置为可选，提高了本方案的实现灵活性，且由于第一基站和第二基站存储的第一基站添加请求的消息结构中UE类型信息的出现属性均为可选，则当第一基站接收到不包含UE类型信息的第一基站添加请求时，不会影响到第一基站的正常工作，保持了通信系统的稳定性。
在第一方面的一种可能实现中，Masked IMEISV信元为第二基站从移动管理实体发送的初始上下文建立请求消息中获取到的；或者，Masked IMEISV信元为第二基站从MME通过S1接口发送的第一切换请求消息中获取到的；或者，Masked IMEISV信元为第二基站通过X2接口从第三基站发送的第二切换请求消息中获取到的，第三基站为UE通过切换接入双连接通信系统之前连接的LTE基站，第二基站为UE通过切换接入双连接通信系统之后连接的LTE基站。
在本申请中，分别结合终端设备初始接入双连接通信系统、终端设备通过S1接口切换进入双连接通信系统以及终端设备通过X2接口切换进入双连接通信系统三种场景，详细介绍了本申请实施例提供的请求处理方法的具体实现方式，拓展了本方案的应用场景，也增强了本方案的可执行性。
第二方面，本申请实施例提供一种请求处理方法。
在UE进入LTE通信系统和NR通信系统构成的双连接通信系统之后，第二基站可以向第一基站发送第一基站添加请求消息，当第一基站添加请求消息中包含终端设备UE的UE类型信息时，第一基站添加请求消息用于供第一基站确定UE的类型，其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站，UE类型信息中至少包含UE的型号，还可以包含UE的操作系统的软件版本号。
在第二方面的一种可能实现中，第二基站上可以预先存储有第一基站添加请求的消息结构，第一基站添加请求的消息结构中至少包含每种类型的信息名称以及与每种类型的信息的出现(presence)属性，其中，UE的UE类型信息的出现属性为可选。
在第二方面的一种可能实现中，本申请实施例提供的请求处理方法还可以包括：在UE初始接入双连接通信系统时，第二基站可以接收到移动管理实体发送的初始上下文建立请求消息，初始上下文建立请求消息中携带有Masked IMEISV信元；或者，在UE通过S1接口切换进入双连接通信系统时，第二基站接收移动管理实体通过S1接口发送的第一切换请求消息，第一切换请求中携带有Masked IMEISV信元；或者，在UE通过X2接口切换进入双连接通信系统时，第二基站接收第三基站通过X2接口发送的第二切换请求消息，第二切换请求消息中携带有Masked IMEISV信元，第三基站为UE通过切换接入双连接通信系统之前连接的LTE基站，第二基站为UE通过切换接入双连接通信系统之后连接的LTE 基站。
在本申请的第二方面中，第二基站还可以执行前述第一方面的各种可能的实现方式中所描述的步骤，第二方面中其他的各种可能的实现方式可以详见前述对第一方面的各种可能的实现方式中的说明。
第三方面，本申请实施例一种基站，所述基站为第一基站，第一基站包括：接收单元和处理单元。接收单元，用于接收第二基站发送的第一基站添加请求消息；处理单元，用于当第一基站添加请求消息中包含终端设备UE的UE类型信息时，根据第一基站添加请求消息确定UE的类型，其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站。
在本申请的第三方面中，第一基站的组成模块还可以执行前述第一方面的各种可能的实现方式中所描述的步骤，详见前述对第一方面以及各种可能的实现方式中的说明。
第四方面，本申请实施例一种基站，所述基站为第二基站，第二基站包括发送单元，用于向第一基站发送第一基站添加请求消息，当第一基站添加请求消息中包含终端设备UE的UE类型信息时，第一基站添加请求消息用于供第一基站确定UE的类型，其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站。
在本申请的第四方面中，第二基站的组成模块还可以执行前述第二方面的各种可能的实现方式中所描述的步骤，详见前述对第二方面以及各种可能的实现方式中的说明。
第五方面，本申请实施例提供了一种基站，所述基站为第一基站，第一基站包括：接收器、处理器和存储器，接收器用于接收第二基站发送的第一基站添加请求消息并存储至存储器；处理器用于当第一基站添加请求消息中包含终端设备UE的UE类型信息时，根据第一基站添加请求消息确定UE的类型，其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站。
在本申请的第五方面中，第一基站的组成模块还可以执行前述第一方面的各种可能的实现方式中所描述的步骤，详见前述对第一方面以及各种可能的实现方式中的说明。
第六方面，本申请实施例提供了一种基站，所述基站为第二基站，第二基站包括：发射器和处理器，发射器用于在处理器确定第一基站添加请求后，向第一基站发送第一基站添加请求消息，当第一基站添加请求消息中包含终端设备UE的UE类型信息时，第一基站添加请求消息用于供第一基站确定UE的类型，其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站。
在本申请的第六方面中，第二基站的组成模块还可以执行前述第二方面的各种可能的实现方式中所描述的步骤，详见前述对第二方面以及各种可能的实现方式中的说明。
第七方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机或处理器上运行时，使得所述计算机或处理器执行上述第一方面或第二方面中任一项所述的方法。
第八方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机或处理器上运行时，使得所述计算机或处理器执行上述第一方面或第二方面中任一项所述的方法。
第九方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于支持通信设备实现上述方面中所涉及的功能，例如，发送或处理上述方法中所涉及的数据和/或信息。在 一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存通信设备必要的程序指令和数据。该芯片系统，可以包括芯片，也可以包括芯片和其他分立器件。
第十方面，本申请还提供了一种通信系统，所述通信系统包括第一基站和第二基站，其中，第一基站用于执行上述第一方面以及各种可能的实现方式中第一基站执行的步骤，第二基站用于执行上述第二方面以及各种可能的实现方式中第二基站执行的步骤。
第十一方面，本申请还提供了一种通信系统，所述通信系统包括第一基站、第二基站及第三基站，其中，第一基站用于执行上述第一方面以及各种可能的实现方式中第一基站执行的步骤，第二基站用于执行上述第二方面以及各种可能的实现方式中第二基站执行的步骤，第三基站用于执行上述第一方面或第二方面以及各种可能的实现方式中第三基站执行的步骤。
本申请第二方面至第十一方面的有益效果，可以参考第一方面。
附图说明
图1为本申请实施例提供的请求处理方法所适用的双连接通信系统的一种结构示意图；
图2为本申请实施例提供的请求处理方法的一种流程示意图；
图3为本申请实施例提供的国际移动设备标识软版号信元的一种结构示意图；
图4为本申请实施例提供的请求处理方法的另一种流程示意图；
图5为本申请实施例提供的请求处理方法的又一种流程示意图；
图6为本申请实施例提供的请求处理方法的再一种流程示意图；
图7为本申请实施例提供的第一基站的一种结构示意图；
图8为本申请实施例提供的第二基站的一种结构示意图；
图9为本申请实施例提供的第一基站的另一种结构示意图；
图10为本申请实施例提供的第二基站的另一种结构示意图。
具体实施方式
本申请实施例提供了一种请求处理方法、相关装置及系统，第一基站可以从第二基站发送的第一基站添加请求中获取至少一个UE的UE类型信息，提供了第二基站获取UE类型信息的方案。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
为了使本技术领域的人员更好地理解本申请实施例中的技术方案，下面结合附图对本申请实施例中的技术方案作进一步详细的说明。在对本申请实施例的技术方案说明之前，首先结合附图对本申请实施例的应用场景进行说明。
本申请实施例的技术方案可应用于至少两代通信系统构成的双连接场景中，作为示例，例如本申请实施例可以应用于LTE通信系统与NR通信系统构成的双连接场景下，具体的，可以包括但不限于LTE-A(LTE Advanced)系统、或LTE-U系统，或LTE授权辅助接入(licensed assisted access，LAA)系统与NR系统所构成的双连接场景下，更具体的，可以适用于以LTE基站为主基站，NR基站为辅基站的LTE-NR双连接(e-utran nr dual connectivity，EN-DC)(以下简称为“EN-DC双连接”)中。当然本申请实施例还可以适用于NR通信系统与第六代通信系统构成的双连接场景下，或者，第六代通信系统与第七代通信系统构成的双连接场景下等，具体此处不做限定。
请参见图1，图1示出了本申请实施例提供的请求处理方法的应用环境的一种网络架构示意图，为本申请提供的技术方案应用于EN-DC双连接场景下的一种场景示意图。所述EN-DC双连接通信系统包含至少一个移动管理实体(mobility management entity，MME)、至少一个LTE基站和至少一个NR基站，应当理解，虽然图1中示出了两个MME、2个LTE基站和2个NR基站，但图1中的示例仅为方便理解本方案，具体MME、LTE基站以及NR基站的数量可以结合实际情况灵活确定。其中，LTE基站指的是LTE通信系统中的基站，也可以称为第四代通信系统中的基站或者演进型基站(evolved node B，eNB或eNodeB)，在EN-DC双连接通信系统中，LTE基站也可以称为主基站(MeNB)；NR基站指的是NR通信系统中的基站，也可以称为第五代通信系统中的基站或者gNB，在EN-DC双连接通信系统中，NR基站也可以称为辅基站(SgNB)。
MME、LTE基站以及NR基站之间可以通过通信接口连接，具体的，MME与LTE基站之间可以通过S1接口进行通信；LTE基站与LTE基站之间可以通过X2接口进行通信；MME与NR基站之间可以通过S1-U接口进行通信，S1-U接口为可选接口；LTE基站与NR基站之间的通信接口也为X2接口。目前协议中规定，MME可以通过S1接口将UE的UE类型信息传输给LTE基站；不同的LTE基站之间可以通过X2接口传递UE类型信息。但却没有对NR基站如何获取到UE类型信息做相关规定。
其中，本申请实施例中所涉及的终端设备，可以是指向用户提供语音和/或数据连通性的无线终端，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(radio access network，RAN)与一个或多个核心网进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(personal communication service，PCS)电话、无绳电话、会话发起协议(session initiation protocol，SIP)话机、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)等设备。无线终端也可以称为系统、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point)、远程终端(remote terminal)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)、用户设备(user device)、或用户装备(user equipment，UE)，具体这里不做限定。
为解决现有技术中NR基站无法获取到UE类型信息的问题，本申请实施例提出如下的请求处理方法。下面结合图2对本申请提供的请求处理方法的具体实现方式进行详细说 明，图2为本申请实施例提供的请求处理方法的一种可能的实施例，方法可以包括：
201、第一基站接收第二基站发送的第一基站添加请求消息。
本申请实施例中，第一基站为第M代通信系统中的基站，第二基站为第N代通信系统中的基站，其中M的取值大于N的取值。具体的，当本申请实施例应用于EN-DC双连接通信系统时，第一基站为NR基站，第二基站为LTE基站，应当理解，本实施例及后续实施例中，仅以本申请实施例应用于EN-DC双连接通信系统场景下进行详细说明。
本申请实施例中，当终端设备初始接入EN-DC双连接通信系统时，或者，当终端设备由LTE通信系统移动至EN-DC通信系统时，第一基站会向第二基站发送第一基站添加请求消息，第一基站添加请求用于指示第一基站为即将接入的UE准备和预留无线资源，具体的，第一基站添加请求中可以包含第一基站添加触发指示信息、所述UE的安全能力信息以及切换限制列表等信息。作为示例，例如，当第一基站为辅基站，第二基站为主基站的情况下，第一基站添加请求可以具体表现为辅基站添加请求(SgNB addition request)，当然，随着网络架构的不断演进，也可以存在第一基站为主基站，第二基站为辅基站的情况，则第一基站添加请求还可以有其他称呼，例如主基站添加请求等，具体此处不做限定。
由于第二基站在向第一基站发送的第一基站添加请求中会携带多种类型的信息，每种类型的信息可以称为一组(group)信息，并将同一类型的信息携带于一个信息元素(information element，IE)(以下简称“信元”)中。为了方便第一基站和第二基站对第一基站添加请求中包含的多种信元的管理，第一基站和第二基站上均可以存储有第一基站添加请求的消息结构，第一基站添加请求的消息结构中至少包含每个信元的名称以及与每个信元一一对应的出现(presence)属性，第一基站添加请求的消息结构中还可以包含与每个信元一一对应的指定关键性(assigned criticality)的属性。
其中，出现属性用于指示与出现属性对应的信元在第一基站添加请求中的出现必要性，作为示例，例如出现属性的属性值可以为M、O或其他属性值等，M为必须(must)的缩写，当某一信元的出现属性为M时，意味着所述信元为第一基站添加请求中必须存在的信元；O为可选(option)的缩写，当某一信元的出现属性为O时，意味着所述信元为第一基站添加请求中必须存在的信元；出现的属性为其他属性值的时候，还可以代表其他含义，此处不一一进行列举。
第一基站在接收到第一基站添加请求后，会解析第一基站添加请求以获取其中包含的多个信元，则对于某个确定的信元既可以出现解析成功，也可以出现解析失败，指定关键性的属性用于指示当某一信元解析失败时第一基站的操作，作为示例，例如指定关键性属性的属性值可以为拒绝(reject)、忽略(ignore)或其他属性值等，当某一信元的指定关键性的属性值为拒绝时，则当第一基站对所述信元解析失败时，第一基站会执行拒绝操作，也即第一基站会拒绝第二基站发送的第一基站添加请求；当某一信元的指定关键性的属性值为忽略时，则当第一基站对所述信元解析失败时，第一基站会执行忽略操作，也即不会对第二基站反馈，而是继续执行其他程序；当第一信元的指定关键性属性为其他属性值时，还可以指示第二基站作其他操作，此处不再一一进行列举。
更具体的，第一基站和第二基站可以通过建立表格、索引或其他类型的方式存储第一基站添加请求的消息结构，此处仅以第一基站和第二基站通过表格的方式存储第一基站添 加请求的消息结构为例，结合如下表1进行详细说明。
表1
Figure PCTCN2020078110-appb-000001
参见表1，表1中示出了第一基站添加请求中包含的多个信元中的四个信元的描述信息，第一个信元的名称为信息类型，所述信元的出现属性的属性值为M，也即第一基站添加请求中必须携带第一基站添加请求的信息类型，所述信元的指定关键性属性的属性值为reject，也即当第一基站对第一基站添加请求的信息类型解析失败时，第一基站执行拒绝操作；第二个信元的名称为UE在NR系统中的安全能力信息，上述信元的出现属性的属性值为M，指定关键性属性的属性值为reject，也即第一基站添加请求中必须携带UE在NR系统中的安全能力信息，若第一基站对UE在NR系统中的安全能力信息解析失败，则执行拒绝操作；此处不再对第三个信元和第四个信元进行详细介绍，但结合第三个信元和第四个信元可知，某一信元的出现属性的属性值与指定关键性属性的属性值之间没有固定的对应关系，也即并不是当信元为可选信元时，指定关键性属性的属性值就是忽略，每个属性值的确定均为结合实际情况确定下来的。应当理解，上述表1中示出的四种信元的具体含义可以结合本领域相关协议进行理解，此处不再对每个信元的具体含义作进一步介绍，且表1中对信元的排序与每个信元在第一基站添加请求中的顺序无关，表1中的举例仅为方便理解本方案，不用于限定本方案。
本申请实施例中，第一基站可以通过X2接口接收第二基站发送的第一基站添加请求消息，在接收到第一基站添加请求消息之后，结合预先存储的第一基站添加请求的消息结构，对第一基站添加请求消息进行解析，以获取第一基站添加请求消息通过多个信元携带的信息。
202、当第一基站添加请求消息中包含终端设备的终端设备类型信息时，第一基站根据第一基站添加请求消息确定终端设备的类型。
本申请实施例中，UE的UE类型信息至少包含UE的型号信息，具体的，不同品牌的UE的型号不同，同一品牌的不同系列的UE型号也可以不同，作为示例，例如UE是手机，则华为的手机和小米的手机为不同型号的手机；作为另一示例，例如华为的商务机系列和荣耀系列也可以视为不同型号的手机。进一步的，UE的类型信息中还可以包含UE的操作系统的软件版本号。具体的，在LTE通信系统和NR通信系统中，第二基站可以将UE的型号信息携带在国际移动设备标识软版号(international mobile station equipment identity and software version number，Masked IMEISV)信元中，但应当理解，在第三代通信系统中， UE的型号信息被携带于国际移动设备标识(international mobile station equipment identity，IMEI)信元中，也即在未来的通信系统中，UE的型号信息也可以被携带于其他信元中，此处不进行限定。
更具体的，如图3所示，Masked IMEISV信元中可以由16位字节组成，所述16位字节组成的信息可以分为三部分，分别为类型分配码(type allocation code，TAC)，序列号(serial number，SNR)和软件版本号(software version number，SVN)，其中TAC的长度为8位字节，可以用于体现每个UE的型号；SNR的长度为6位字节，用于唯一标识一类UE型号中的某一个特定的UE，但在Masked IMEISV信元中，为了避免基站泄露UE的唯一标识号，SNR的右边4位字节的值均置1，从而避免信息安全的问题；SVN的长度为2位字节，用于体现每个UE的操作系统的软件版本号。
本申请实施例中，由于第一基站添加请求中增加了UE类型信息，则第一基站添加请求中需要扩展新的信元来携带UE类型信息，与此同时，第一基站和第二基站存储的第一基站添加请求的消息结构中需要增加扩展信元的描述信息。扩展信元的描述信息中至少包含扩展信元的名称和扩展信元的出现属性，还可以包含扩展信元的指定关键性的属性。具体的，结合如下表2，对扩展信元为Masked IMEISV信元的情况进行详细描述。
表2
Figure PCTCN2020078110-appb-000002
参见表2，表2仅示出了第一基站添加请求包含的五个信元的描述信息，由于前四个信元已经在结合表1进行举例时做了一次详细描述，此处不再赘述。参见表2中关于Masked IMEISV信元的描述信息，Masked IMEISV信元的出现属性为“O”，也即Masked IMEISV信元的出现属性为可选，也即第一基站添加请求中可以出现Masked IMEISV信元，也可以不出现Masked IMEISV信元。
具体的，对于第一基站这一侧，第一基站在接收到第一基站添加请求之后，可以判断第一基站添加请求中是否存在Masked IMEISV信元，若存在Masked IMEISV信元，则解析第一基站添加请求，并获取其中携带的UE类型信息；若不存在Masked IMEISV信元，则只解析并获取第一基站添加请求中包含的其他信息，不执行UE类型信息的获取操作。
对于第二基站这一侧，第一基站添加请求中是否存在Masked IMEISV信元，可以由第二基站结合其他情况进一步确定，作为示例，例如通信服务的供应商可以在第二基站上预 先设定第一基站添加请求中是否包含Masked IMEISV信元；作为另一示例，例如由于UE的UE类型用于供基站确定UE的至少一个特性，则第二基站也可以根据UE的UE类型确定UE对至少一个特性的兼容情况，仅在第二基站根据UE的UE类型确定所述UE对至少一个特性的兼容性较差的情况下，第二基站将所述UE的UE类型信息发送给第一基站；作为另一示例，例如第二基站也获取第一基站和第二基站之间的通信通道的安全性级别，当第一基站和第二基站之间的通信通道的安全性级别较高时，向第一基站发送的第一基站添加请求中包含Masked IMEISV信元；应当理解，第一基站还可以结合其他情况进一步确定第一基站添加请求中是否包含Masked IMEISV信元。将Masked IMEISV信元的出现属性设置为可选，提高了本方案的实现灵活性，且由于第一基站和第二基站存储的第一基站添加请求的消息结构中Masked IMEISV信元的出现属性均为可选，则当第一基站接收到不包含Masked IMEISV信元的第一基站添加请求时，不会影响到第一基站的正常工作，保持了通信系统的稳定性。
继续结合表2中关于Masked IMEISV信元的描述信息，Masked IMEISV信元的指定关键性的属性为忽略。具体的，对于第一基站这一侧，第一基站在在接收到第一基站添加请求之后，若第一基站添加请求中是否存在Masked IMEISV信元，则第一基站解析第一基站添加请求，并获取其中携带的UE类型信息，若在解析获取UE类型信息中解析失败，则第一基站执行忽略操作，也即不向第二基站反馈解析失败的信息。对于第二基站这一侧，由于Masked IMEISV信元的指定关键性的属性为忽略，则即使第二基站向第一基站发送的第一基站添加请求中携带有Masked IMEISV信元，第二基站也不可以默认为第一基站已经获得了UE的UE类型信息。
本申请实施例中，第一基站在接收到第二基站发送的第一基站添加请求后，可以判断第一基站添加请求中是否包含UE的UE类型信息，当第一基站添加请求消息中包含UE的UE类型信息时，可以解析第一基站添加请求并获取其中携带的UE类型信息，进而第一基站可以根据UE类型信息确定UE的类型。具体的，当UE类型信息携带于Masked IMEISV信元时，第一基站可以根据Masked IMEISV信元中的TAC确定UE的类型，或者第一基站可以根据Masked IMEISV信元中的TAC和SVN确定UE的类型，将携带UE类型信息的信元确定为Masked IMEISV信元，提高了本方案的可执行性，且由于Masked IMEISV信元中包含的SNR的右边4位字节的值均置1，从而避免了UE的真实的唯一标识序列号被泄露，提高了信息传输过程的安全性；进一步的，当UE的操作系统的版本不同时，UE支持的特性也可能会不同，也即同一型号且操作系统版本不同的UE可以被划分为不同类型的UE，由于Masked IMEISV信元中可以同时包括UE的型号以及操作系统的版本号，则采用Masked IMEISV信元作为携带UE类型信息的信元时，可以提高第一基站在确定UE类型过程中的精度。应当理解，当UE类型信息携带于IMEI或其他类型的信元中时，可以结合其他类型的信元中包含的其他信息确定UE的类型，此处不进行限定。
203、第一基站根据终端设备的终端设备类型确定终端设备的至少一个特性。
本申请实施例中，第一基站上可以预先配置有终端设备管理信息，具体的，第一基站可以通过表格、索引、数组或其他形式存储前述终端设备管理信息。更具体的，终端设备管理信息中至少包括UE类型和特性，终端设备管理信息中包含多种UE类型，每种UE类 型对应至少一个特性。其中，特性指的是通信技术在不断改进或改变过程中引入的新技术，作为示例，例如：省电模式、连续接收(discontinuous reception，DRX)、载波聚合(carrier aggregation，CA)和/或物理小区标识(physical cell identity，PCI)冲突检测等，应当理解，此处对特性的举例仅为方便理解本方案，不用于限定本方案，对于每个特性的具体含义均可结合本领域相关协议进行理解，此处不做详细介绍。
对于第一基站上存储的所有特性，并不是每种类型的UE都全部支持，第一基站预置的终端设备管理信息中还可以包含与每种UE类型的每个特性一一对应的归属名单。归属名单用于指示与归属名单对应的UE是否支持与归属名单对应的特性，也即当与归属名单对应的UE执行与归属名单对应的特性时，是否会导致UE运行异常。具体的，归属名单可以包括白名单、黑名单和灰名单，其中，白名单指的是与白名单对应的UE支持与白名单对应的特性，黑名单指的是与黑名单对应的UE不支持与黑名单对应的特性，灰名单指的是由运营商确定与灰名单对应的UE是否支持与灰名单对应的特性，以下仅以第一基站以终端设备管理列表的形式存储前述终端设备管理信息为例，结合表3进行详细描述。
表3
终端设备的类型 特性 归属名单
类型1 省电模式 黑名单
类型1 非连续接收 黑名单
类型2 省电模式 白名单
类型2 载波聚合 白名单
类型3 物理小区标识冲突检测 灰名单
类型3 非连续接收 白名单
类型4 非连续接收 灰名单
参见表3，表3仅示出了第一基站存储的终端设备管理列表中的部分内容，包含4种类型的终端设备，其中，与类型1的UE对应有两个特性，分别为省电模式和非连续接收，与类型1的UE的省电模式和非连续接收对应的归属名单均为黑名单，也即类型1的UE不支持省电模式，也不支持非连续接收；与类型2的UE对应有两个特性，分别为省电模式和载波聚合，与类型1的UE的省电模式和载波聚合对应的归属名单均为白名单，也即类型2的UE既支持省电模式，也支持载波聚合；与类型3的UE对应有两个特性，分别为物理小区标识冲突检测和非连续接收，与类型3的UE的物理小区标识冲突检测对应的归属名单为灰名单，也即类型3的UE是否支持物理小区标识冲突检测需要运营商进一步确定，与类型3的UE的非连续接收对应的归属名单为白名单，也即类型3的UE支持非连续接收，此处不再对类型4的UE做进一步描述，应当理解，表3中的举例仅为方便理解本方案，具体对不同类型的UE支持的特性，以及归属名单的确定应该结合UE的实际情况灵活确定，此处不作限定。
可选的，终端设备管理列表中归属名单可以仅包含黑名单和灰名单，也即除了根据终端设备管理列表中确定哪些类型的UE不支持哪些特性外，对于第一基站上的其他特性，可以全部默认为支持。结合表3进行举例，也即终端设备管理列表中不存在表3中第四行、第五行以及第七行中的数据。由于一般情况下，UE对第一基站的大部分特性都是支持的， 终端设备管理列表的归属名单中仅包含黑名单和灰名单，不仅可以减少终端设备管理列表占用的存储空间，也有利于降低第一基站对UE进行差异化管理的工作负荷。
可选的，终端设备管理信息中包含的多种UE类型中可以仅包含对特性的支持性较差的UE类型，也即支持的特性较少的UE类型，具体的，可以为当某一种UE类型的UE不支持的特性数量达到某一阈值时或者当某一种UE类型的UE支持的特性数量低于某一阈值时，将所述一种UE类型视为对特性的支持性较差的UE类型。
作为一种实现方式，终端设备管理列表中仅包含对特性的支持性较差的UE类型。
具体的，当归属名单中包含白名单、黑名单和灰名单时，第一基站在确定UE的UE类型之后，可以根据UE的UE类型与终端管理列表进行匹配，若终端设备管理列表中不存在所述UE类型，则可以将第一基站上的所有特性作为与所述UE对应的至少一个特性，并可以视为所述UE支持第一基站上的所有特性；若终端设备管理列表中存在所述UE类型，则将终端设备管理列表中记录的、与所述UE类型对应的至少一个特性确定为所述UE的至少一个特性，并根据终端设备管理列表确定所述至少一个特性中每个特性的归属名单是白名单还是黑名单还是灰名单。
当终端设备管理列表中仅包含黑名单和灰名单时，第一基站在确定UE的UE类型之后，可以根据UE的UE类型与终端管理列表进行匹配，若归属名单中不存在所述UE类型，则可以将第一基站上的所有特性作为与所述UE对应的至少一个特性，并可以视为所述UE支持第一基站上的所有特性；若终端设备管理列表中存在所述UE类型，则将终端设备管理列表中记录的、与所述UE类型对应的至少一个特性确定为所述UE的至少一个特性，并根据终端设备管理列表确定所述至少一个特性中每个特性的归属名单是黑名单还是灰名单，将第一基站上的除所述至少一个特性之外的其他特性视为所述UE支持的特性。
本申请的部分实施例中，终端设备管理信息中包含的多种UE类型中可以仅包含对特性的支持性较差的UE类型，也即第一基站可以仅管理对特性的支持性较差的UE类型，减少了第一基站的工作负荷。
作为另一种实现方式，终端设备管理列表中可以包含所有的UE类型，且归属名单中包含白名单、黑名单和灰名单时，则第一基站在确定UE的UE类型之后，可以根据UE的UE类型对终端管理列表进行查询，以确定与所述UE对应的至少一个特性，以及与所述UE的每个特性对应的归属名单是白名单还是黑名单还是灰名单。每种UE类型的UE以及每种UE类型的UE的每个特性均在终端管理列表中存在对应的记录，提高了第一基站在UE管理过程中的严谨性。
应当理解，由于当归属名单中仅包含黑名单和灰名单时，终端设备管理列表中不可能存在所有的UE类型，因此不对终端设备管理列表中包含所有的UE类型，且归属名单中仅包含黑名单和灰名单这一情况进行论述。
204、第一基站根据终端设备的至少一个特性对终端设备进行管理。
本申请实施例中，第一基站在通过步骤203可以获取到UE的至少一个特性，并确定与所述UE的至少一个特性中每个特性对应的归属名单，也即可以获取到UE是否支持所述至少一个特性中的每个特性。具体的，对于归属名单为白名单的特性或者UE支持的特性，第一基站可以直接执行；对于归属名单为黑名单的特性，第一基站可以禁止启用；对于归 属名单为灰名单的特性，第一基站可以暂不启用，由运营商进一步确定所述UE是否支持所述特性。第一基站在获取到UE的UE类型之后，可以根据UE类型确定UE的至少一个特性，并进而根据UE的至少一个特性对UE进行差异化管理，由于特性指的是在通信技术演进或改变过程中的新技术，根据UE的至少一个特性对UE进行差异化管理，也即确定UE对第一基站上的特性的支持情况，从而第一基站确定对UE执行哪些特性，避免导致对UE执行了不支持的特性之后出现的异常掉线等情况，提高用户的通信体验。
205、当第一基站添加请求消息中不包含终端设备UE的UE类型信息时，第一基站不获取终端设备类型信息。
应当理解，步骤202至步骤204与步骤205不能同时存在。
本申请实施例中，当第一基站为NR基站且第二基站为LTE基站时，第一基站接收到第二基站发送的第一基站添加请求，在第一基站添加请求中携带UE的UE类型信息的情况下，从而第一基站可以根据UE的UE类型对所述UE进行差异化管理，以提供更良好的用户体验。由于至少一个UE的UE类型信息是包含在第一基站添加请求中的，而第一基站添加请求是触发第一基站进入UE的双连接通信系统的请求，从而第一基站可以在为UE提供通信服务的初始即获取到UE的类型信息，则保证了UE从进入双连接通信系统之后即可以获取到良好的通信服务；且本方案的实施是基于现有的网络架构实现的，也即不会给现有的网络架构造成很大的改变，提高了本方案的可实现性。
为便于更好的理解和实施本申请实施例的上述方案，下面还是以本申请实施例应用于EN-DC双连接通信系统中为例进行具体说明。根据终端设备进入EN-DC双连接通信系统的进入方式不同，又可以做进一步划分，具体的，终端设备可以为初始接入EN-DC双连接通信系统，也可以为终端设备通过S1接口切换进入EN-DC双连接通信系统，还可以为终端设备通过X2接口切换进入EN-DC双连接通信系统，由于前述三种场景下的具体执行步骤有所不同，以下分别结合前述三种应用场景进行举例。
一、初始接入EN-DC双连接通信系统
本申请实施例中，参见图4，图4为本申请实施例提供的请求处理方法的一种可能的实施例，方法可以包括：
401、移动管理实体向LTE基站发送初始上下文建立请求消息。
本实施例中，UE在初始接入EN-DC双连接通信系统时，可以由MME为UE选择一个LTE基站(也即第二基站)，并向所述LTE基站发送初始上下文建立请求(initial context setup request)消息，所述初始上下文建立请求消息中包含用于携带UE类型信息的Masked IMEISV信元，从而所述LTE基站能够从初始上下文建立请求消息中获取到Masked IMEISV信元，以获得UE的UE类型信息。
402、LTE基站向移动管理实体发送初始上下文建立完成消息。
本实施例中，LTE基站在接收到MME发送的初始上下文建立请求消息之后，可以与终端设备进行信息交互，以获取UE的能力信息(capability information)，命令UE开启安全模式(security mode)，并可以向UE发送无线资源控制(radio resource control，RRC)重配置(RRC Conn reconfiguration)消息的方式，以使终端设备获取所述LTE基站上的无线资源的配置信息，在前述操作均完成之后，可以向MME发送初始上下文建立完成(initial  context setup response)消息。
403、LTE基站向NR基站发送辅基站添加请求消息。
本实施例中，LTE基站在完成了初始上下文的建立之后，可以通过LTE基站与NR基站(也即第一基站)之间的X2接口向NR基站发送辅基站添加请求(SgNB addition request)消息，则所述辅基站添加请求消息可以扩展Masked IMEISV信元，以将UE的UE类型信息发送给NR基站。应当理解，当本申请实施例应用于EN-DC双连接时，辅基站添加请求消息为图2所描述的实施例中的第一基站添加请求，辅基站添加请求还可以包含其他信息，具体辅基站添加请求包含哪些信息可以结合图2实施例中的描述以及本领域相关协议进行理解，此处不再作详细赘述。
404、NR基站向LTE基站发送辅基站添加请求响应消息。
本实施例中，NR基站在接收到辅基站添加请求消息之后，会向LTE基站对应的辅基站添加请求响应(SgNB addition request acknowledge)消息，所述辅基站添加请求响应消息中包含有所述NR基站的无线资源的配置信息。
405、LTE基站向终端设备发送RRC重配置消息。
本实施例中，LTE基站在接收到NR基站发送的辅基站添加请求响应消息之后，可以再次向终端设备发送RRC重配置消息(RRC Conn reconfiguration)，以使终端设备获取到NR基站上的数据承载的配置信息，进而终端设备可以根据所述LTE基站和所述NR基站上的无线资源的配置信息执行接入操作。
二、通过S1接口切换进入EN-DC双连接通信系统
本申请实施例中，参见图5，图5为本申请实施例提供的请求处理方法的一种可能的实施例，方法可以包括：
501、移动管理实体向目标LTE基站发送切换请求消息。
本实施例中，目标LTE基站为终端设备执行切换接入操作后连接的LTE基站(也即第二基站)。MME可以通过S1接口向目标LTE基站发送切换请求(handover request)消息(也即第一切换请求消息)，用于要求目标LTE基站为通过切换接入到EN-DC双连接通信系统的UE准备和预留所需要的资源，第一切换请求消息中包含用于携带UE类型信息的Masked IMEISV信元，从而目标LTE基站能够从第一切换请求消息中获取到Masked IMEISV信元，以获得UE的UE类型信息。
502、目标LTE基站向移动管理实体发送切换请求确认消息。
本实施例中，目标LTE基站在接收到切换请求消息后判断是否允许接入，在允许接入的情况下向MME发送切换请求响应(handover request acknowledge)消息，以使MME配合源LTE基站释放源LTE基站(也即第三基站)的无线资源以及转发源LTE基站承载的数据等操作，执行完毕后，目标LTE基站可以接收到RRC配置完成(RRC Conn reconfiguration complete)消息，进而进入步骤503，其中，源LTE基站为终端设备执行切换接入操作前连接的LTE基站。
503、目标LTE基站向NR基站发送辅基站添加请求消息。
504、NR基站向目标LTE基站发送辅基站添加请求响应消息。
505、目标LTE基站向终端设备发送RRC重配置消息。
本实施例中，步骤503至步骤505与图4描述的实施例中的步骤403至步骤405类似，区别仅在于步骤403至步骤405是初始接入时的LTE基站与NR基站进行信息交互，步骤503至步骤505中是终端设备执行切换接入操作后连接的目标LTE基站与NR基站进行信息交互，此处不再做赘述。
三、通过X2接口切换进入EN-DC双连接通信系统
本申请实施例中，参见图6，图6为本申请实施例提供的请求处理方法的一种可能的实施例，方法可以包括：
601、源LTE基站向目标LTE基站发送切换请求消息。
本实施例中，源LTE基站(也即第三基站)为终端设备执行切换接入操作前连接的LTE基站，目标LTE基站(也即第二基站)为终端设备执行切换接入操作后连接的LTE基站，源LTE基站可以通过X2接口直接向目标LTE基站发送切换请求消息(也即第二切换请求消息)，从而目标LTE基站可以从第二切换请求消息中的Masked IMEISV信元中获取到UE的UE类型信息，具体的，第二切换请求消息包含的内容与步骤501中的第一切换请求消息包含的内容类似，此处不再赘述。
602、目标LTE基站向NR基站发送辅基站添加请求消息。
603、NR基站向LTE基站发送辅基站添加请求响应消息。
本实施例中，步骤602和步骤603与图5描述的实施例中的步骤503和步骤504类似，此处不再做赘述。
604、目标LTE基站向源LTE基站发送切换请求响应消息。
本实施例中，目标LTE基站在接收到NR基站(也即第一基站)发送的辅基站添加请求响应消息之后，可以向源LTE基站发送切换请求响应消息，以触发源LTE基站执行无线资源释放、承载数据转发等操作，并在执行完毕后，可以由目标LTE基站通知MME进行路径切换。
本申请实施例中，以上分别结合终端设备初始接入EN-DC双连接通信系统、终端设备通过S1接口切换进入EN-DC双连接通信系统以及终端设备通过X2接口切换进入EN-DC双连接通信系统三种场景，详细介绍了本申请实施例提供的请求处理方法的具体实现方式，拓展了本方案的应用场景，也增强了本方案的可执行性。
为便于更好的实施本申请实施例的上述方案，下面还提供用于实施上述方案的相关装置。具体参阅图7，图7为本申请实施例提供的第一基站的一种结构示意图，第一基站700包括：接收单元701和处理单元702。接收单元701，用于接收第二基站发送的第一基站添加请求消息；处理单元702，用于当第一基站添加请求消息中包含终端设备UE的UE类型信息时，第一基站根据第一基站添加请求消息确定UE的类型，其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站。
本申请实施例中，第一基站为NR基站，第二基站为LTE基站，接收单元701接收到第二基站发送的第一基站添加请求，在第一基站添加请求中携带UE的UE类型信息的情况下，从而处理单元702可以根据UE的UE类型对UE进行差异化管理，以提供更良好的用户体验。由于至少一个UE的UE类型信息是包含在第一基站添加请求中的，而第一基站添加请求是触发第一基站进入UE的双连接通信系统的请求，从而第一基站可以在为UE提供 通信服务的初始即获取到UE的类型信息，则保证了UE从进入双连接通信系统之后即可以获取到良好的通信服务；且本方案的实施是基于现有的网络架构实现的，也即不会给现有的网络架构造成很大的改变，提高了本方案的可实现性。
在一种可能的设计中，处理单元702，还用于根据UE的UE类型确定UE的至少一个特性，并根据UE的至少一个特性对UE进行管理。
在一种可能的设计中，UE类型信息携带于国际移动设备标识软版号Masked IMEISV信元中。
在一种可能的设计中，第一基站上预先存储有第一基站添加请求的消息结构，第一基站添加请求的消息结构中至少包含每种类型的信息的信息名称以及每种类型的信息的出现(presence)属性，其中，UE类型信息的出现属性为可选。
在一种可能的设计中，Masked IMEISV信元为第二基站从移动管理实体MME发送的初始上下文建立请求消息中获取到的；或者，Masked IMEISV信元为第二基站从MME发送的第一切换请求消息中获取到的；或者，Masked IMEISV信元为第二基站从第三基站发送的第二切换请求消息中获取到的，第三基站为LTE基站。
本申请实施例提供的第一基站700用于执行图2至图6对应的方法实施例中第一基站所执行的方法，故本申请实施例可以参考图2至图6对应的方法实施例中的相关部分进行理解，此处不再赘述。
接下来，请参阅图8所示，图8为本申请实施例提供的第二基站的一种结构示意图，第二基站800包括：发送单元801。发送单元801，用于向第一基站发送第一基站添加请求消息，当第一基站添加请求消息中包含终端设备UE的UE类型信息时，第一基站添加请求消息用于供第一基站确定UE的类型，其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站。
在一种可能的设计中，UE类型信息携带于国际移动设备标识软版号Masked IMEISV信元中。
在一种可能的设计中，第二基站上预先存储有第一基站添加请求的消息结构，第一基站添加请求的消息结构中至少包含每种类型的信息名称以及与每种类型的信息的出现(presence)属性，其中，UE的UE类型信息的出现属性为可选。
在一种可能的设计中，第二基站800还包括接收单元802，具体用于：接收移动管理实体MME发送的初始上下文建立请求消息，初始上下文建立请求消息中携带有Masked IMEISV信元；或者，接收移动管理实体MME发送的第一切换请求消息，第一切换请求中携带有Masked IMEISV信元；或者，接收第三基站发送的第二切换请求消息，第二切换请求消息中携带有Masked IMEISV信元，第三基站为LTE基站。
本申请实施例提供的第二基站800用于执行图2至图6对应的方法实施例中第二基站所执行的方法，故本申请实施例可以参考图2至图6对应的方法实施例中的相关部分进行理解，此处不再赘述。
接下来介绍本申请实施例提供的另一种基站，请参阅图9所示，为本申请实施例提供的第一基站的一种结构示意图，第一基站900包括：接收器901、发射器902、处理器903和存储器904(其中第一基站900中的处理器903的数量可以一个或多个，图9中以一个 处理器为例)，其中，处理器903可以包括应用处理器9031和通信处理器9032。在本申请的一些实施例中，接收器901、发射器902、处理器903和存储器904可通过总线或其它方式连接。
存储器904可以包括只读存储器和随机存取存储器，并向处理器903提供指令和数据。存储器904的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory，NVRAM)。存储器904存储有处理器和操作指令、可执行模块或者数据结构，或者它们的子集，或者它们的扩展集，其中，操作指令可包括各种操作指令，用于实现各种操作。
处理器903控制终端设备的操作。具体的应用中，终端设备的各个组件通过总线系统耦合在一起，其中总线系统除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都称为总线系统。
上述本申请实施例揭示的方法可以应用于处理器903中，或者由处理器903实现。处理器903可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器903中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器903可以是通用处理器、数字信号处理器(digital signal processing，DSP)、微处理器或微控制器，还可进一步包括专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。该处理器903可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器904，处理器903读取存储器904中的信息，结合其硬件完成上述方法的步骤。
接收器901可用于接收输入的数字或字符信息，以及产生与终端设备的相关设置以及功能控制有关的信号输入。发射器902可用于通过第一接口输出数字或字符信息；发射器902还可用于通过第一接口向磁盘组发送指令，以修改磁盘组中的数据；发射器902还可以包括显示屏等显示设备。
本申请实施例中，第一基站900用于执行前述第一基站执行的请求处理方法。具体的，接收器901接收第二基站发送的第一基站添加请求消息，当第一基站添加请求消息中包含终端设备UE的UE类型信息时，处理器903根据第一基站添加请求消息确定UE的类型，其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站。
本申请实施例中，第一基站为NR基站，第二基站为LTE基站，接收器901接收到第二基站发送的第一基站添加请求，在第一基站添加请求中携带UE的UE类型信息的情况下，处理器903可以根据UE的UE类型对UE进行差异化管理，以提供更良好的用户体验。由于至少一个UE的UE类型信息是包含在第一基站添加请求中的，而第一基站添加请求是触发第一基站进入UE的双连接通信系统的请求，从而第一基站可以在为UE提供通信服务的初始即获取到UE的类型信息，则保证了UE从进入双连接通信系统之后即可以获取到良好 的通信服务；且本方案的实施是基于现有的网络架构实现的，也即不会给现有的网络架构造成很大的改变，提高了本方案的可实现性。
在一种可能的设计中，处理器903还用于根据UE的UE类型确定UE的至少一个特性，并根据UE的至少一个特性对UE进行管理。
在一种可能的设计中，UE类型信息携带于国际移动设备标识软版号Masked IMEISV信元中。
在一种可能的设计中，存储器904中预先存储有第一基站添加请求的消息结构，第一基站添加请求的消息结构中至少包含每种类型的信息的信息名称以及每种类型的信息的出现(presence)属性，其中，UE类型信息的出现属性为可选。
在一种可能的设计中，Masked IMEISV信元为第二基站从移动管理实体MME发送的初始上下文建立请求消息中获取到的；或者，Masked IMEISV信元为第二基站从MME发送的第一切换请求消息中获取到的；或者，Masked IMEISV信元为第二基站从第三基站发送的第二切换请求消息中获取到的，第三基站为LTE基站。
本申请实施例提供的第一基站900用于执行图2至图6对应的方法实施例中第一基站所执行的方法，故本申请实施例可以参考图2至图6对应的方法实施例中的相关部分进行理解，此处不再赘述。
接下来介绍本申请实施例提供的另一种基站，请参阅图10所示，第二基站1000包括：接收器1001、发射器1002、处理器1003和存储器1004(其中第二基站1000中的处理器1003的数量可以一个或多个，图10中以一个处理器为例)，其中，处理器1003可以包括应用处理器10031和通信处理器10032。在本申请的一些实施例中，接收器1001、发射器1002、处理器1003和存储器1004可通过总线或其它方式连接。
存储器1004可以包括只读存储器和随机存取存储器，并向处理器1003提供指令和数据。存储器1004的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory，NVRAM)。存储器1004存储有处理器和操作指令、可执行模块或者数据结构，或者它们的子集，或者它们的扩展集，其中，操作指令可包括各种操作指令，用于实现各种操作。
处理器1003控制终端设备的操作。具体的应用中，终端设备的各个组件通过总线系统耦合在一起，其中总线系统除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都称为总线系统。
上述本申请实施例揭示的方法可以应用于处理器1003中，或者由处理器1003实现。处理器1003可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1003中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1003可以是通用处理器、数字信号处理器(digital signal processing，DSP)、微处理器或微控制器，还可进一步包括专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。该处理器1003可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处 理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1004，处理器1003读取存储器1004中的信息，结合其硬件完成上述方法的步骤。
接收器1001可用于接收输入的数字或字符信息，以及产生与终端设备的相关设置以及功能控制有关的信号输入。发射器1002可用于通过第一接口输出数字或字符信息；发射器1002还可用于通过第一接口向磁盘组发送指令，以修改磁盘组中的数据；发射器1002还可以包括显示屏等显示设备。
本申请实施例中，第二基站1000用于执行前述第二基站执行的请求处理方法。具体的，发射器1002用于在处理器1003确定第一基站添加请求后，向第一基站发送第一基站添加请求消息，当第一基站添加请求消息中包含终端设备UE的UE类型信息时，第一基站添加请求消息用于供第一基站确定UE的类型，其中，第一基站为新空口NR基站，第二基站为长期演进LTE基站。
在一种可能的设计中，UE类型信息携带于国际移动设备标识软版号Masked IMEISV信元中。
在一种可能的设计中，第二基站上预先存储有第一基站添加请求的消息结构，第一基站添加请求的消息结构中至少包含每种类型的信息名称以及与每种类型的信息的出现(presence)属性，其中，UE的UE类型信息的出现属性为可选。
在一种可能的设计中，接收器1001体用于：接收移动管理实体MME发送的初始上下文建立请求消息，初始上下文建立请求消息中携带有Masked IMEISV信元；或者，接收移动管理实体MME发送的第一切换请求消息，第一切换请求中携带有Masked IMEISV信元；或者，接收第三基站发送的第二切换请求消息，第二切换请求消息中携带有Masked IMEISV信元，第三基站为LTE基站。
本申请实施例中还提供一种包括请求处理指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如前述图2至图6所示实施例描述的方法中第一基站所执行的步骤。
本申请实施例中还提供一种包括请求处理指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如前述图2至图6所示实施例描述的方法中第二基站所执行的步骤。
本申请实施例中还提供一种计算机可读存储介质，该计算机可读存储介质中存储有通信系统间转移的指令，当其在计算机上运行时，使得计算机执行如前述图2至图6所示实施例描述的方法中第一基站所执行的步骤。
本申请实施例中还提供一种计算机可读存储介质，该计算机可读存储介质中存储有通信系统间转移的指令，当其在计算机上运行时，使得计算机执行如前述图2至图6所示实施例描述的方法中第二基站所执行的步骤。
本申请实施例中还提供一种通信系统，所述通信系统包括第一基站和第二基站，第一基站为前述图7或前述图9所示实施例描述的第一基站，第二基站为前述图8或前述图10所示实施例描述的第二基站。
本申请实施例中还提供一种通信系统，所述通信系统包括第一基站、第二基站和第三基站，第一基站执行如前述图2至图6所示实施例描述的方法中第一基站所执行的步骤， 第二基站执行如前述图2至图6所示实施例描述的方法中第二基站所执行的步骤，第三基站执行如前述图2至图6所示实施例描述的方法中第三基站所执行的步骤。
另外需说明的是，以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。另外，本申请提供的装置实施例附图中，模块之间的连接关系表示它们之间具有通信连接，具体可以实现为一条或多条通信总线或信号线。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过专用硬件包括专用集成电路、专用CPU、专用存储器、专用元器件等来实现。一般情况下，凡由计算机程序完成的功能都可以很容易地用相应的硬件来实现，而且，用来实现同一功能的具体硬件结构也可以是多种多样的，例如模拟电路、数字电路或专用电路等。但是，对本申请而言更多情况下软件程序实现是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘、U盘、转移硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD)等。

Claims (14)

  1. 一种请求处理方法，其特征在于，所述方法包括：
    第一基站接收第二基站发送的第一基站添加请求消息；
    当所述第一基站添加请求消息中包含终端设备UE的UE类型信息时，所述第一基站根据所述第一基站添加请求消息确定所述UE的类型；
    其中，所述第一基站为新空口NR基站，所述第二基站为长期演进LTE基站。
  2. 根据权利要求1所述的处理方法，其特征在于，所述方法还包括：
    所述第一基站根据所述UE的UE类型确定所述UE的至少一个特性；
    所述第一基站根据所述UE的至少一个特性对所述UE进行管理。
  3. 根据权利要求1或2所述的处理方法，其特征在于，所述UE类型信息携带于国际移动设备标识软版号Masked IMEISV信元中。
  4. 根据权利要求3所述的处理方法，其特征在于，
    所述Masked IMEISV信元为所述第二基站从移动管理实体MME发送的初始上下文建立请求消息中获取到的；或者，
    所述Masked IMEISV信元为所述第二基站从MME发送的第一切换请求消息中获取到的；或者，
    所述Masked IMEISV信元为所述第二基站从第三基站发送的第二切换请求消息中获取到的，所述第三基站为LTE基站。
  5. 一种请求处理方法，其特征在于，所述方法包括：
    第二基站向第一基站发送第一基站添加请求消息，当所述第一基站添加请求消息中包含终端设备UE的UE类型信息时，所述第一基站添加请求消息用于供所述第一基站确定所述UE的类型；
    其中，所述第一基站为新空口NR基站，所述第二基站为长期演进LTE基站。
  6. 根据权利要求5所述的处理方法，其特征在于，所述UE类型信息携带于国际移动设备标识软版号Masked IMEISV信元中。
  7. 根据权利要求6所述的处理方法，其特征在于，所述方法还包括：
    所述第二基站接收移动管理实体MME发送的初始上下文建立请求消息，所述初始上下文建立请求消息中携带有所述Masked IMEISV信元；或者，
    所述第二基站接收移动管理实体MME发送的第一切换请求消息，所述第一切换请求中携带有所述Masked IMEISV信元；或者，
    所述第二基站接收第三基站发送的第二切换请求消息，所述第二切换请求消息中携带有所述Masked IMEISV信元，所述第三基站为LTE基站。
  8. 一种基站，其特征在于，所述基站为第一基站，所述第一基站包括：
    接收单元，用于接收第二基站发送的第一基站添加请求消息；
    处理单元，用于当所述第一基站添加请求消息中包含终端设备UE的UE类型信息时，根据所述第一基站添加请求消息确定所述UE的类型；
    其中，所述第一基站为新空口NR基站，所述第二基站为长期演进LTE基站。
  9. 根据权利要求8所述的基站，其特征在于，
    所述处理单元，还用于根据所述UE的UE类型确定所述UE的至少一个特性，并根据所述UE的至少一个特性对所述UE进行管理。
  10. 根据权利要求8或9所述的基站，其特征在于，所述UE类型信息携带于国际移动设备标识软版号Masked IMEISV信元中。
  11. 根据权利要求10所述的基站，其特征在于，
    所述Masked IMEISV信元为所述第二基站从移动管理实体MME发送的初始上下文建立请求消息中获取到的；或者，
    所述Masked IMEISV信元为所述第二基站从MME发送的第一切换请求消息中获取到的；或者，
    所述Masked IMEISV信元为所述第二基站从第三基站发送的第二切换请求消息中获取到的，所述第三基站为LTE基站。
  12. 一种基站，其特征在于，所述基站为第二基站，所述第二基站包括：
    发送单元，用于向第一基站发送第一基站添加请求消息，当所述第一基站添加请求消息中包含终端设备UE的UE类型信息时，所述第一基站添加请求消息用于供所述第一基站确定所述UE的类型；
    其中，所述第一基站为新空口NR基站，所述第二基站为长期演进LTE基站。
  13. 根据权利要求12所述的基站，其特征在于，所述UE类型信息携带于国际移动设备标识软版号Masked IMEISV信元中。
  14. 根据权利要求13所述的基站，其特征在于，
    所述第二基站还包括接收单元，所述接收单元，具体用于：
    接收移动管理实体MME发送的初始上下文建立请求消息，所述初始上下文建立请求消息中携带有所述Masked IMEISV信元；或者，
    接收移动管理实体MME发送的第一切换请求消息，所述第一切换请求中携带有所述Masked IMEISV信元；或者，
    接收第三基站发送的第二切换请求消息，所述第二切换请求消息中携带有所述Masked IMEISV信元，所述第三基站为LTE基站。
PCT/CN2020/078110 2019-03-28 2020-03-06 一种请求处理方法、相关装置及系统 WO2020192387A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910243889.9 2019-03-28
CN201910243889.9A CN111757317B (zh) 2019-03-28 2019-03-28 一种请求处理方法、相关装置及系统

Publications (1)

Publication Number Publication Date
WO2020192387A1 true WO2020192387A1 (zh) 2020-10-01

Family

ID=72610986

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/078110 WO2020192387A1 (zh) 2019-03-28 2020-03-06 一种请求处理方法、相关装置及系统

Country Status (2)

Country Link
CN (1) CN111757317B (zh)
WO (1) WO2020192387A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023103683A1 (zh) * 2021-12-09 2023-06-15 中兴通讯股份有限公司 数据传输方法及其装置、存储介质、程序产品
WO2023239277A1 (en) * 2022-06-10 2023-12-14 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes and methods for handling masked imeisv in a wireless communication network

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018060968A1 (en) * 2016-09-30 2018-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Core network awareness of user equipment, ue, state

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101977239B (zh) * 2010-11-11 2015-04-22 华为技术有限公司 一种制定策略的方法、策略服务器及网关
WO2018060918A1 (en) * 2016-09-28 2018-04-05 Ecole Polytechnique Federale De Lausanne (Epfl) Semiconductor device comprising a three-dimensional field plate

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018060968A1 (en) * 2016-09-30 2018-04-05 Telefonaktiebolaget Lm Ericsson (Publ) Core network awareness of user equipment, ue, state

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "UE context handling during inter RAT handover", 3GPP TSG-RAN WG2 #101BIS, R2-1804802, 5 April 2018 (2018-04-05), XP051415161, DOI: 20200509153913X *
ERICSSON: "UE context handling during inter RAT handover", 3GPP TSG-RAN WG2 #102, R2-1807041, 10 May 2018 (2018-05-10), XP051463964, DOI: 20200509154010X *
ERICSSON: "UE context handling during inter RAT handover(TP to 38.300)", 3GPP TSG-RAN WG2 #AH-1807, R2-1810412, 22 June 2018 (2018-06-22), XP051526193, DOI: 20200509154145X *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023103683A1 (zh) * 2021-12-09 2023-06-15 中兴通讯股份有限公司 数据传输方法及其装置、存储介质、程序产品
WO2023239277A1 (en) * 2022-06-10 2023-12-14 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes and methods for handling masked imeisv in a wireless communication network

Also Published As

Publication number Publication date
CN111757317A (zh) 2020-10-09
CN111757317B (zh) 2021-12-28

Similar Documents

Publication Publication Date Title
US11622339B2 (en) Communication method and communications apparatus
US11611912B2 (en) Cell reselection method and related device
US11751262B2 (en) Electronic apparatus, a central node apparatus and a network side apparatus, a transmission method and a configuration method
US20220369392A1 (en) Communication Method and Related Device
WO2017210888A1 (zh) 寻呼方法、装置及系统
US20210377847A1 (en) Communication method, terminal device, and core network device
WO2020019961A1 (zh) 通信方法、接入网设备和终端设备
WO2022171051A1 (zh) 一种通信方法和通信装置
TW201427453A (zh) 處理細胞選擇的方法及其通訊裝置
WO2020221223A1 (zh) 通信方法、装置和系统
WO2020248582A1 (en) Methods and apparatuses for logical tsn bridge
US20210360517A1 (en) Method and Apparatus for Obtaining System Information
WO2020192387A1 (zh) 一种请求处理方法、相关装置及系统
US20220272577A1 (en) Communication method and communication apparatus
WO2020052463A1 (zh) 通信方法和网元
US20210176698A1 (en) Method for updating system information, terminal, and network side device
CN110784912B (zh) 一种会话对应关系的管理方法和终端设备
WO2019019020A1 (en) DEVICE DEVICE COMMUNICATION METHOD AND DEVICE (D2D)
CN110474742B (zh) 一种确定rrm测量配置的方法及设备
WO2020164470A1 (zh) 通信方法及其装置、系统
CN111132210B (zh) 测量事件中的SpCell确定方法和装置
CN111194084B (zh) 信息传输方法及装置
CN111194072A (zh) 多波束场景下监听寻呼的方法及装置
JP2021510993A (ja) セルアクセスプロシージャの改善
CN109479225B (zh) 一种接入异制式小区的方法以及相关设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20778999

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20778999

Country of ref document: EP

Kind code of ref document: A1