WO2019191943A1 - 一种无线通信方法及设备 - Google Patents

一种无线通信方法及设备 Download PDF

Info

Publication number
WO2019191943A1
WO2019191943A1 PCT/CN2018/081928 CN2018081928W WO2019191943A1 WO 2019191943 A1 WO2019191943 A1 WO 2019191943A1 CN 2018081928 W CN2018081928 W CN 2018081928W WO 2019191943 A1 WO2019191943 A1 WO 2019191943A1
Authority
WO
WIPO (PCT)
Prior art keywords
capability
access system
terminal
access
identifier
Prior art date
Application number
PCT/CN2018/081928
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 华为技术有限公司
Priority to PCT/CN2018/081928 priority Critical patent/WO2019191943A1/zh
Publication of WO2019191943A1 publication Critical patent/WO2019191943A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a wireless communication method and device.
  • the base station when a radio resource is allocated to a user equipment (UE), the base station first needs to know the access standard capability of the UE.
  • the access standard capability of the UE refers to an access system that the UE can support, and the UE is connected. Access capability to the access system.
  • Access systems include universal terrestrial radio access (UTRA), evolved UTRA (E-UTRA), new radio (NR), and the like. Then, the base station allocates radio resources to the UE based on the access system capability of the UE, thereby maximizing the use efficiency of the radio resources.
  • the current method for the base station to acquire the access system capability of the UE is as follows: after the UE and the base station complete the Radio Resource Control (RRC) connection, if the core network stores the access system capability of the UE, the core network will The access system capability of the UE is sent to the base station through an Initial Context Setup Request, so that the base station acquires the access system capability of the UE. If the core network does not save the access system capability of the UE, the base station sends a UE Capability Request message to the UE to instruct the UE to report its access system capability. Alternatively, when the UE performs cell handover, the base station receives the access system capability of the UE forwarded by the source base station of the UE.
  • RRC Radio Resource Control
  • the base station when receiving the access system capability of a UE forwarded by the core network or other base stations, the base station may not be able to accurately know all the access system capabilities of the UE.
  • the access system capability of a certain UE that is forwarded by the core network or other base station only includes the access standard identifier of the UTRA and the corresponding capability field.
  • the base station may not be able to accurately know whether the UE further supports other access systems.
  • the base station may not be able to accurately know the access system capability of the UE.
  • the embodiment of the present application provides a wireless communication method and device, which are used to solve the problem that a base station may not be able to accurately learn the access system capability of the UE.
  • the embodiment of the present application provides a wireless communication method, including: receiving, by a terminal, a terminal capability request message sent by a network device, and transmitting terminal capability information to the network device, where the network device may be a base station.
  • the terminal capability request message is used to indicate that the UE reports the access system capability.
  • the terminal capability information carries an access system identifier that is not supported by the terminal.
  • the terminal adds an access system identifier that is not supported by the terminal in the terminal capability information, so that when the base station acquires the access system capability of the terminal, the terminal can not know the access system supported by the terminal, and can also learn that the terminal does not know.
  • the supported access system can reduce the probability that the base station can initiate the capability query process again, thereby reducing the overhead of air interface signaling and reducing the delay of terminal access and service startup.
  • the terminal capability information may carry at least one access standard identifier of the terminal that is not supported by the terminal in the terminal capability request message, and may also carry at least one access carried by the terminal capability request message.
  • the access system identifier that is not supported by the terminal part in the system identifier.
  • the terminal capability information includes a capability system list, where the capability system list includes at least one supported access system identifier and a corresponding capability field, and at least one unsupported access system identifier, any one.
  • the capability field corresponding to the access system identifier is used to represent the access capability of the terminal to access the access system corresponding to any one of the access system identifiers.
  • the base station can determine whether the terminal supports the access system corresponding to the access standard identifier by determining whether the capability information field of the access system identifier is carried in the terminal capability information, so that the access system of the terminal can be clearly known. ability.
  • the terminal capability request message carries at least one access system identifier. If the terminal supports the first access system corresponding to the first access system identifier, the capability system list includes the first access system identifier and the corresponding capability field. If the terminal does not support the first access system, the capability system list includes the first access system identifier, and does not include the capability field corresponding to the first access system identifier.
  • the first access system identifier is any access system identifier in the access system identifier carried by the terminal capability request message.
  • the terminal may carry the identifier and capability field of the access system in the terminal capability information for the supported access system, and the terminal capability for the unsupported access system.
  • the information carries the identifier of the access system, and does not carry the capability field, so that the base station can determine whether the terminal supports the access system corresponding to the access standard identifier by determining whether the terminal capability information carries the capability field corresponding to the access system identifier. Therefore, the access system capability of the terminal can be clearly known.
  • the terminal constructs the terminal capability information by setting the first access system identifier and the corresponding field to be filled in the capability system list. If the terminal supports the access system corresponding to the first access system identifier, the terminal fills the capability field corresponding to the first access system identifier in the corresponding to-be-filled field.
  • the base station can determine whether the terminal supports the access system corresponding to the access standard identifier by determining whether the capability information field of the access system identifier is carried in the terminal capability information, so that the access system of the terminal can be clearly known. ability.
  • the terminal capability request message carries at least one access system identifier.
  • the terminal capability information includes a request list and a capability system list, where the request list includes an access system identifier carried by the terminal capability request message, where the capability system list includes at least one supported access system identifier and corresponding Capability field.
  • the base station may determine, according to the access system identifier included in the capability standard list, the access system supported by the terminal, and determine, according to the access system identifier included in the request list and not included in the capability standard list, the terminal does not support the connection. Into the system, so that the access system capability of the terminal can be clearly known.
  • the request list includes a second access standard identifier. If the terminal supports the second access system corresponding to the second access system identifier, the capability system list includes the second access system identifier and the corresponding capability field, where the second access standard identifier is Any access system identifier in the access system identifier carried by the terminal capability request message.
  • the terminal adds the request list to the terminal capability information, so that the base station can determine the access mode supported by the terminal according to the access system identifier included in the capability standard list, according to the capability list in the request list.
  • the included access system identifier determines an access system that the terminal does not support.
  • the terminal constructs the terminal capability information by filling the request list with an access system identifier carried by the terminal capability request message. If the terminal supports the second access system, the terminal sets the second access standard identifier and the corresponding to-be-filled field in the capability formula list, and is in the corresponding to-be-filled field. Filling in the capability field corresponding to the second access system identifier.
  • the base station may determine, according to the access system identifier included in the capability standard list, the access system supported by the terminal, and determine, according to the access system identifier included in the request list and not included in the capability standard list, the terminal does not support the connection. Into the system, so that the access system capability of the terminal can be clearly known.
  • the terminal capability information carrying capability list and the unsupported capability list include at least one supported access standard identifier and a corresponding capability field.
  • the unsupported capability system list includes at least one unsupported access system identifier.
  • the base station may determine the access standard supported by the terminal according to the access system identifier included in the capability standard list, and determine the access system that the terminal does not support according to the access system identifier included in the unsupported capability standard list, thereby making it clear Know the access system capabilities of the terminal.
  • the capability system list includes the third access system identifier and the corresponding capability field, if The terminal does not support the third access system, and the unsupported capability list includes the third access standard identifier.
  • the third access system identifier is any access system identifier in the access system identifier carried by the terminal capability request message.
  • the terminal adds a non-supported capability list to the terminal capability information, so that the base station can determine the access mode supported by the terminal according to the access system identifier included in the capability standard list, and is included according to the unsupported capability standard list.
  • the access standard identifier determines an access system that the terminal does not support.
  • the terminal constructs the terminal capability information by: if the terminal supports the third access system, the terminal sets the third in the capability system list The access system identifier and the corresponding field to be filled are filled in, and the capability field corresponding to the third access system identifier is filled in the corresponding to-be-filled field. If the terminal does not support the third access system, the terminal sets the third access standard identifier in the unsupported capability system list.
  • the base station may determine the access standard supported by the terminal according to the access system identifier included in the capability standard list, and determine the access system that the terminal does not support according to the access system identifier included in the unsupported capability standard list, thereby making it clear Know the access system capabilities of the terminal.
  • the embodiment of the present application provides a wireless communication method, including: the first network device sends a terminal capability request message to the terminal, where the terminal capability request message is used to indicate that the UE reports the access system capability.
  • the first network device receives the terminal capability information reported by the terminal, where the terminal capability information carries an access standard identifier that is not supported by the terminal, and the terminal capability information may be any one of the foregoing first aspect or the foregoing first aspect. Terminal capability information as described in the design.
  • the first network device may be a base station that establishes an RRC connection with the terminal.
  • the terminal adds an access system identifier that is not supported by the terminal in the terminal capability information, so that when the base station acquires the access system capability of the terminal, the terminal can not know the access system supported by the terminal, and can also learn that the terminal does not know.
  • the supported access system can reduce the probability that the base station can initiate the capability query process again, thereby reducing the overhead of air interface signaling and reducing the delay of terminal access and service startup.
  • the first network device determines an access system capability of the terminal according to the terminal capability information. Or the first network device forwards the terminal capability information to the second network device when the RRC connection is established with the terminal, so that the second network device saves the access system capability of the terminal, where The second network device can be a core network device. Or the first network device forwards the terminal capability information to the third network device when the terminal is switched to the third network device, so that the third network device determines the access mode of the terminal.
  • the capability wherein the third network device may be a target base station to be accessed when the terminal performs cell handover.
  • the base station may also notify the core network of the access system capability of the terminal, or may access the terminal when the terminal is switched to another base station. Forward to other base stations.
  • the determining, by the first network device, the access system capability of the terminal according to the terminal capability information includes: if the capability system list includes a capability field corresponding to the second access system identifier The first network device determines that the terminal supports the second access system corresponding to the second access system identifier, and the second access system identifier is any access system included in the capability system list. logo. Alternatively, if the capability field corresponding to the second access system identifier is not included in the capability list, the first network device determines that the terminal does not support the second access system.
  • the base station can determine whether the terminal supports the access system corresponding to the access standard identifier by determining whether the terminal capability information carries the capability field corresponding to the access system identifier, so that the access system capability of the terminal can be obtained.
  • the first network device determines the access system capability of the terminal according to the terminal capability information, including: if the capability system list includes a fourth access system identifier, and the a capability field corresponding to the four access system identifiers, where the first network device determines that the terminal supports the fourth access system corresponding to the fourth access system identifier, and the fourth access system identifier is the request list Any access system identifier included in the file. Or the first network device determines that the terminal does not support the fourth connection, if the capability mode list does not include the capability information field corresponding to the fourth access system identifier and the fourth access system identifier. Enter the system.
  • the terminal adds the request list to the terminal capability information, so that the base station can determine the access mode supported by the terminal according to the access system identifier included in the capability standard list, according to the capability list in the request list.
  • the included access system identifier determines an access system that the terminal does not support.
  • the first network device determines, according to the terminal capability information, the access standard capability of the terminal, where the first network device determines that the terminal supports the sixth access standard identifier.
  • the access system, the sixth access system identifier is any access system identifier in the capability system list.
  • the first network device determines that the terminal does not support the access system corresponding to the seventh access system identifier, and the seventh access system identifier is any access system in the unsupported capability system list.
  • logo the terminal adds a non-supported capability list to the terminal capability information, so that the base station can determine the access mode supported by the terminal according to the access system identifier included in the capability standard list, and is included according to the unsupported capability standard list.
  • the access standard identifier determines an access system that the terminal does not support.
  • the embodiment of the present application provides a wireless communication method, including: a first network device receives and saves terminal capability information sent by a second network device, where the terminal capability information carries an access standard identifier that is not supported by the terminal. .
  • the first network device sends the terminal capability information to a third network device.
  • the first network device may be a core network device, and the second network device may be a base station that establishes an RRC connection with the terminal.
  • the terminal capability information may be the terminal capability information described in the above first aspect or any one of the above first aspects.
  • the access system capability of a terminal that is saved by the core network device includes an access standard identifier that is not supported by the terminal, and a supported access system identifier, so that the core network device may forward to the base station, including The supported access system identifier and the access system capability of the supported access system identifier, so that when the base station receives the access system capability of the terminal forwarded by the core network, the base station can clearly know the access system supported by the terminal, and can also The access system that is not supported by the terminal is learned, so that the probability of the base station re-initiating the capability query process is reduced, thereby reducing the overhead of the air interface signaling and reducing the delay of the terminal access and the service start.
  • the embodiment of the present application provides a method for wireless communication, including: receiving, by a first network device, terminal capability information that is sent by a second network device, where the terminal capability information carries an access system identifier that is not supported by the terminal.
  • the first network device determines an access system capability of the terminal according to the terminal capability information.
  • the first network device may be a core network device, or may be a base station that the terminal accesses before performing cell handover.
  • the terminal capability information may be the terminal capability information described in the above first aspect or any one of the above first aspects.
  • the method for determining, by the first network device, the access system capability of the terminal according to the terminal capability information may be the method described in the foregoing second aspect or any one of the foregoing second aspects.
  • the access system capability of a terminal that is saved by the core network device includes an access standard identifier that is not supported by the terminal, and a supported access system identifier, so that the core network device may forward to the base station, including The supported access system identifier and the access system capability of the supported access system identifier, so that when the base station receives the access system capability of the terminal forwarded by other base stations, in addition to explicitly knowing the access standard supported by the terminal, The access system that is not supported by the terminal is learned, so that the probability of the base station re-initiating the capability query process is reduced, thereby reducing the overhead of the air interface signaling and reducing the delay of the terminal access and the service start.
  • the embodiment of the present application further provides a terminal, including: a receiving module, configured to receive a terminal capability request message from a network device, where the terminal capability request message is used to indicate that the UE reports the access mode capability.
  • the constructing module is configured to construct terminal capability information, where the terminal capability information carries an access standard identifier that is not supported by the terminal.
  • a sending module configured to send, to the network device, the terminal capability information configured by the constructing module.
  • the terminal capability information may be the terminal capability information described in the foregoing first aspect or any one of the foregoing first aspects.
  • a first network device in the embodiment of the present application, where the first network device may be a source base station that establishes an RRC connection with the terminal, and the following uses the first network device as a source base station as an example for description.
  • the source base station includes: a sending module, configured to send a terminal capability request message to the terminal, where the terminal capability request message is used to indicate that the UE reports the access mode capability.
  • the receiving module is configured to receive terminal capability information reported by the terminal, where the terminal capability information carries an access standard identifier that is not supported by the terminal.
  • the terminal capability information may be the terminal capability information described in the foregoing first aspect or any one of the foregoing first aspects.
  • the base station also includes a determination module. And a determining module, configured to determine, according to the terminal capability information, an access system capability of the terminal.
  • the sending module is further configured to forward the terminal capability information to the second network device when the RRC connection is established with the terminal, so that the second network device saves the The access system capability of the terminal.
  • the sending module is further configured to: when the terminal is switched to the third network device, forward the terminal capability information to the third network device, so that the third The network device determines the access system capability of the terminal.
  • the determining module is specifically configured to: if the capability system list includes a capability field corresponding to the second access system identifier, determine that the terminal supports the second access standard identifier
  • the second access system identifier is any access system identifier included in the capability system list.
  • the capability field corresponding to the second access system identifier is not included in the capability list, it is determined that the terminal does not support the second access system.
  • the determining module is specifically configured to: if the capability system list includes a fourth access system identifier and a capability field corresponding to the fourth access system identifier, determine the terminal support The fourth access system identifier corresponding to the fourth access system identifier, where the fourth access system identifier is any access system identifier included in the request list.
  • the capability model list does not include the capability information field corresponding to the fourth access system identifier and the fourth access system identifier, determining that the terminal does not support the fourth access system.
  • the determining module is specifically configured to: determine that the terminal supports an access system corresponding to the sixth access standard identifier, where the sixth access system identifier is in the capability system list. Any access system identifier. Or determining that the terminal does not support the access system corresponding to the seventh access system identifier, where the seventh access system identifier is any access system identifier in the unsupported capability system list.
  • the embodiment of the present application further provides a second network device, where the second network device may be a core network device, and the second network device is used as a core network device as an example.
  • the core network device includes: receiving And a module, configured to receive terminal capability information from the base station, where the terminal capability information carries an access system identifier that is not supported by the terminal. And a saving module, configured to save the terminal capability information received by the receiving module. And a sending module, configured to send, to the second network device, terminal capability information saved by the saving module.
  • the embodiment of the present application further provides a third network device, where the third network device may be a target base station that is accessed when the terminal performs cell handover, and the following uses the third network device as a destination base station as an example.
  • the destination base station includes: a receiving module, configured to receive terminal capability information sent by the second network device, where the terminal capability information carries an access system identifier that is not supported by the terminal.
  • a determining module configured to determine, according to the terminal capability information, an access system capability of the terminal.
  • the determining module may be the determining module described in any one of the sixth aspect or the sixth aspect.
  • the embodiment of the present application further provides a wireless communication device, where the device includes a communication interface, a processor, and a memory, where the communication interface is used for transmitting and receiving signals, and the memory is used to store a software program, and the processing is performed.
  • the apparatus is for reading a software program stored in the memory and implementing the method provided by any one of the aspects of any one of the first aspect to the fourth aspect.
  • the embodiment of the present application further provides a computer storage medium, where the software program stores a software program, and the software program can implement the first to fourth aspects when being read and executed by one or more processors. Any of the aspects or any one of the aspects of the design provided by the method.
  • the embodiment of the present application provides a computer program product comprising instructions, when executed on a computer, causing the computer to perform any one of the aspects of the first aspect to the fourth aspect or any one of the aspects. Design the method described.
  • the embodiment of the present application provides a chip, where the chip is connected to a memory, and is used for reading and executing a software program stored in the memory, so as to implement the foregoing aspects to the fourth aspect. Any of the aspects or any one of the aspects of the design provided by the method.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a base station acquiring an access system capability of a terminal according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of another base station acquiring an access system capability of a terminal according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of another base station acquiring an access system capability of a terminal according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a wireless communication apparatus according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a wireless communication apparatus according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a wireless communication apparatus according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a wireless communication apparatus according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a wireless communication apparatus according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a wireless communication apparatus according to an embodiment of the present application.
  • the wireless communication method provided by the present application can be applied to a communication system.
  • the architecture of the communication system includes a base station 101 and a terminal device 102, and may further include a core network device 103 and a base station 104.
  • the base station 104 may be a base station that the terminal device 102 accesses after cell handover.
  • the communication system may be various types of communication systems, for example, may be long term evolution (LTE), may be a fifth generation (5G) communication system, or may be universal terrestrial wireless access ( Universal terrestrial radio access (UTRA), evolved UTRA (E-UTRAN), new radio (NR), GSM/EDGE radio access network-circuit switched (GSM EDGE radio access network-circuit switched, GERAN- CS), GSM/EDGE radio access network–packet switched (GERAN-PS), code division multiple access (CDMA) 2000-1 XRTT, and multiple radio access Multi-RAT Dual-Connectivity (MR-DC), etc., can also be a hybrid architecture of multiple communication systems, such as LTE and 5G hybrid architecture.
  • LTE long term evolution
  • 5G fifth generation
  • UTRA Universal terrestrial radio access
  • E-UTRAN evolved UTRA
  • NR new radio
  • GSM/EDGE radio access network-circuit switched GSM EDGE radio access network-circuit switched
  • GERAN-PS GSM/EDGE radio access network–packet
  • the base station 101 and the base station 104 may be a common base station (such as a Node B or an eNB), may be a new radio controller (NR controller), and may be a gNode B (gNB) in a 5G system, which may be
  • the centralized unit may be a new radio base station, which may be a radio remote module, may be a micro base station, may be a relay, may be a distributed network element, or may be a receiving point. (Transmission Reception Point, TRP) or Transmission Point (TP) or any other wireless access device, but the embodiment of the present application is not limited thereto.
  • the terminal device 102 also known as a User Equipment (UE) is a device that provides voice and/or data connectivity to a user, for example, a handheld device with a wireless connection function, an in-vehicle device, and the like.
  • UE User Equipment
  • Common terminals include, for example, mobile phones, tablets, notebook computers, PDAs, mobile internet devices (MIDs), wearable devices such as smart watches, smart bracelets, pedometers, and the like.
  • the core network device 103 may be a mobility management entity (MME), may be a serving gateway (SGW), or may be an Access Management Function (AMF) in a 5G system. Etc., the core network device can provide further network connections, such as a telephone network and/or a data communication network (eg, the Internet).
  • the base station can be connected to the core network device through a link (for example, an S1 interface).
  • the access capability of the UE to access various access systems is related to its software and hardware configuration.
  • the base station needs to first understand the access system capability of the UE.
  • the access system capability of the UE refers to an access system that the UE can support, and the access capability of the UE to access the access system. Then, the UE is allocated radio resources based on the access system capability of the UE, thereby maximizing the use efficiency of the radio resources.
  • Types of access systems include UTRA, E-UTRAN, NR, GERAN-CS, GERAN-PS, CDMA2000-1 XRTT, and MR-DC.
  • the UE After the UE completes the radio resource control (RRC) connection with the base station, if the core network stores the access system capability of the UE, the capability of the UE is sent to the initial context setup request (Initial Context Setup Request).
  • the base station is as shown in FIG. 2, so that the base station acquires the access system capability of the UE.
  • the base station After the UE completes the RRC connection with the base station, if the core network does not maintain the access system capability of the UE, that is, the initial Context Setup Request message sent by the core network to the base station does not carry the access system capability of the UE, the base station cannot The core network obtains the access system capability of the UE, so that the base station needs to initiate a capability query process to query the UE for the capabilities of each access system, as shown in FIG.
  • the base station sends a terminal capability request message to the UE, where the terminal capability request message is used to indicate that the UE reports the access system capability.
  • the terminal capability request message may carry at least one access system identifier, and the access system corresponding to the at least one access system identifier is an access system that the UE needs to report. For example, when the UE camps on the E-UTRAN, the base station carries the identifiers of the E-UTRAN, the UTRA, and the NR in the terminal capability request message to instruct the UE to report the access capabilities corresponding to the E-UTRAN, the UTRA, and the NR.
  • the naming of the terminal capability request message is different in each access system.
  • the terminal capability request message is named as the UE Capability Request.
  • the terminal capability request message is named UE Capability Enquiry.
  • the message sent by the base station to indicate that the UE reports the access capability corresponding to each access system is collectively referred to as a terminal capability request message, and may be used by the base station to indicate the UE in the NR system.
  • the message for reporting the access capability corresponding to each access system is named as another name, such as XX. It should be understood that if the XX can also implement the function implemented by the terminal capability request message in the embodiment of the present application, the XX can also be understood as the terminal capability request message in the embodiment of the present application.
  • the UE assembles terminal capability information according to the terminal capability request message, and sends the information to the base station.
  • the terminal capability information includes an identifier of an access system supported by the UE and a corresponding access capability in an access system that the UE needs to report.
  • the terminal capability information includes the access system identifier and the corresponding capability field, and the capability field is used. Determining the access capability of the UE to access the access system corresponding to the access standard identifier. If the access system is not supported by the UE, the access capability identifier is not included in the terminal capability information, and the corresponding capability field is not included.
  • the base station indicates, in the terminal capability request message, that the UE reports the access capability of the UTRA, the E-UTRAN, and the NR.
  • the UE supports UTRA and E-UTRAN, and does not support NR. Therefore, the terminal capability information carries the UTRA identifier and the corresponding capability field, the E-UTRAN identifier, and the corresponding capability field.
  • the naming of the terminal capability information is different in each access system. For example, in UTRA, the terminal capability information is named as UE Capability Response. In E-UTRAN, the terminal capability information is named UE Capability Information.
  • the message carrying the access system capability of the terminal is collectively referred to as the terminal capability information in the embodiment of the present application.
  • the message carrying the terminal access capability of the terminal may be named as another name, such as XX. It should be understood that if the XX can also implement the function implemented by the terminal capability information in the embodiment of the present application, the XX can also be understood as the terminal capability information in the embodiment of the present application.
  • the access standard capability of the terminal can be carried in the terminal capability information based on the code of the ASN structure, and the access standard capability of the terminal can be realized through the code of the ASN structure:
  • the UE-Capability RAT-ContainerList is a capability system list, which includes an access system identifier supported by the terminal.
  • the UE-Capability RAT-Container is used to indicate the supported access system capability, and the rat-Type is used to indicate the access system.
  • ueCapabilityRAT-Container is the capability field corresponding to the access system.
  • the base station saves the terminal capability information that is sent by the UE, and notifies the core network by using the UE Capability Indicator message.
  • the core network may send the access mode capability of the UE to the base station accessed by the UE.
  • the access standard capability of the UE needs to be forwarded to the target base station. If the handover involves the core network device, the access system capability of the UE is transparently transmitted to the core network device through the source base station, and then transparently transmitted by the core network device to the destination base station.
  • the process in which the source base station forwards the access standard capability of the UE to the target base station may be as shown in FIG. 4 .
  • the source base station sends a handover request (Handover Request) to the target base station when the UE is determined to be handed over to the target base station, where the Handover Request carries the access system capability of the UE.
  • the access system capability of the UE is obtained by the source base station based on the terminal capability information reported by the UE, or derived from the access system capability of the UE forwarded by the core network device.
  • the target base station determines, according to the access system capability of the UE in the Handover Request message, and the current configuration context of the UE, that is, the radio resource information configured by the source base station for the UE, to determine the radio resource used by the UE in the handover.
  • the message is then sent to the source base station through a Handover Request ACK message.
  • the access system capability of the UE is saved.
  • the target base station has an ambiguity in interpreting the capability of each access system in the access system capability of the UE.
  • the access system capability of the UE includes only the E-UTRAN capability, that is, only the access system identifier of the E-UTRAN and the corresponding capability field are included, and the target base station cannot know whether the UE supports other access systems because there are two Kind of possible:
  • the source base station queries the access system capability of the UE, multiple access systems are requested, for example, the E-UTRAN system and the NR system are simultaneously requested.
  • the UE only supports the E-UTRAN standard and does not support the NR system. Therefore, the UE only reports the access capability of the E-UTRAN standard.
  • the destination base station cannot know the actual capacity of the access system that the UE does not report. Therefore, if the destination base station needs the access system capability, the capability query process can be initiated again, thereby increasing the air interface cost and the service start delay.
  • Multiple means two or more.
  • the embodiment of the present application provides a wireless communication method and device, which are used to solve the problem that a base station may not be able to accurately learn the access system capability of the UE.
  • the method and the device are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • FIG. 5 a flowchart of a method for wireless communication provided by the present application.
  • the wireless communication method provided by the present application can be applied to the communication system shown in FIG. 1.
  • the method can be specifically as follows.
  • the element names included in the terminal capability request such as the names of elements such as lists and fields, are only an exemplary description, and the naming of each element in the terminal capability information is not limited.
  • the terminal Before the terminal reports the access standard capability, the terminal may first establish an RRC connection with the first network device.
  • the first network device may be a base station. After the terminal establishes an RRC connection with the first network device, if the initial context setting request sent by the second network device to the first network device does not carry the access system capability of the terminal, step S501 is performed, where the second network is performed.
  • the device can be a core network device.
  • the wireless communication method provided by the embodiment of the present application will be described below by taking the first network device as the base station and the second network device as the core network device as an example.
  • the base station sends a terminal capability request message to the terminal.
  • the terminal capability request message is used to indicate that the UE reports the access system capability.
  • the terminal capability request message may carry at least one access system identifier to instruct the terminal to report the access capability corresponding to the at least one access system identifier.
  • the access capability corresponding to an access system identifier may refer to the wireless access capability of the access system corresponding to the access mode identifier of the terminal.
  • the terminal constructs terminal capability information according to the terminal capability request message sent by the base station.
  • the terminal capability information carries an access standard identifier that is not supported by the terminal.
  • the terminal capability information may carry the access standard identifier that is not supported by all the terminals in the at least one access system identifier carried in the terminal capability request message, and may also carry at least one access terminal identifier carried in the terminal capability request message. Supported access system identification.
  • the terminal adds an access system identifier that is not supported by the terminal in the terminal capability information, so that when the base station acquires the access system capability of the terminal, the terminal can not know the access system supported by the terminal, and can also learn that the terminal does not know.
  • the access mode is supported, so that the probability of the base station re-initiating the capability query process is reduced, thereby reducing the overhead of the air interface signaling and reducing the delay of the terminal access and service start.
  • the terminal capability information may carry an access standard identifier that is not supported by the terminal in any of the following three manners:
  • the terminal capability information includes a capability system list, where the capability system list includes at least one supported access system identifier and a corresponding capability field, and at least one unsupported access system identifier.
  • the capability field corresponding to the access system identifier can be set as an optional field.
  • the access system identifier includes the access system identifier and the corresponding capability field, if the terminal supports the access system corresponding to the access system identifier, . If the terminal does not support the access system corresponding to the access system identifier, the capability standard list includes the access system identifier, and the capability field corresponding to the access system identifier is not included.
  • the terminal can construct the terminal capability information by adding an access system identifier carried in the terminal capability request to the access system list included in the terminal capability information.
  • the terminal capability information For the access mode identifier carried in the terminal capability request message, if the terminal supports the access system, the terminal capability information carries a corresponding field to be filled, and the first connection is filled in the corresponding field to be filled. The capability field corresponding to the entry ID. If the terminal does not support the access system, the corresponding capability field is not carried.
  • the terminal can be implemented by the following code:
  • the UE-Capability RAT-ContainerList is a capability standard list, which includes the access system capability that the terminal needs to report.
  • the UE-Capability RAT-Container is used to indicate the access system capability of the terminal, and the rat-Type is used to indicate the access system.
  • the ueCapabilityRAT-Container is the capability field corresponding to the access system, where ueCapabilityRAT-Container is set to an optional field. If the terminal does not support the access system indicated by the rat-Type, the rat-CapabilityRAT-Container does not have the rat-Type.
  • the corresponding ueCapability RAT-Container field, or the ueCapability RAT-Container field corresponding to the rat-Type in the UE-Capability RAT-Container is empty.
  • the terminal capability information carries a request list and a capability system list, where the request list includes an access system identifier carried by the terminal capability request message, and the capability system list includes an access system identifier supported by the terminal and a corresponding capability field.
  • the request list may be added to the terminal capability information, where the request list includes the access standard identifier carried in the terminal capability request message.
  • the access system identifier includes the access system identifier and the corresponding capability field, if the terminal supports the access system corresponding to the access system identifier, .
  • the terminal can construct the terminal capability information by the following manner: the terminal fills the at least one access system identifier carried in the terminal capability request message in the request list. And setting, by the access system identifier, the access system identifier in the capability standard list, and the access system identifier in the access system identifier that is included in the terminal capability request message, and the terminal supporting the access system corresponding to the second access system identifier The corresponding field to be filled is filled in, and the corresponding capability field corresponding to the access system identifier is filled in the corresponding field to be filled.
  • the terminal can implement the second method by the following code:
  • the UE-Capability RAT-ContainerList is a capability standard list, which includes an access standard identifier supported by the terminal.
  • the UE-Capability RAT-Container is used to indicate the supported access system capability, and the rat-Type is used to indicate the access system.
  • ueCapabilityRAT-Container is the capability field corresponding to the access system.
  • the UE-CapabilityRATRequest is a request list, which includes an access system identifier carried in the terminal capability request.
  • Manner 3 The terminal capability information carrying capability system list and the unsupported capability system list, where the capability system list includes an access system identifier supported by the terminal and a corresponding capability field.
  • the unsupported capability list includes the access standard identifiers that are not supported by the terminal.
  • a list of unsupported capability formats can be added to the terminal capability information.
  • the access system identifier includes the access system identifier and the corresponding capability field, if the terminal supports the access system corresponding to the access system identifier, . If the terminal supports the access system corresponding to the access system identifier, the access system identifier is included in the unsupported capability system list.
  • the terminal may construct the terminal capability information by using any of the access system identifiers in the access system identifier carried by the terminal capability request message, and if the terminal supports the access system corresponding to the access system identifier, the terminal The access system identifier and the corresponding field to be filled are set in the capability system list, and the capability field corresponding to the access system identifier is filled in the corresponding field to be filled. If the terminal does not support the access system corresponding to the access standard identifier, the terminal sets the access standard identifier in the unsupported capability system list.
  • the terminal can implement mode 3 through the following code:
  • the UE-Capability RAT-ContainerList is a capability standard list, which includes an access standard identifier supported by the terminal.
  • the UE-Capability RAT-Container is a supported access system capability, the rat-type is used to indicate the access system, and the ueCapability RAT-Container is the capability field corresponding to the access system.
  • UE-CapabilityRATRequest is a list of unsupported capability specifications, including access system identifiers that are not supported by the terminal.
  • the terminal sends the constructed terminal capability information to the base station.
  • the base station After receiving the terminal capability information of the terminal, the base station determines the access system capability of the terminal.
  • the base station may determine the access system capability of the terminal by using any of the access system identifiers in the capability standard list, if The capability system list includes the capability field corresponding to the access system identifier, and the base station determines that the terminal supports the access system corresponding to the access system identifier. If the capability field corresponding to the access system identifier is not included in the capability list, the base station determines that the terminal does not support the access system of the access system identifier.
  • the base station can determine the access system capability of the terminal by using any of the access system identifiers in the request list, if the capability standard list is used. The base station determines that the terminal supports the access system corresponding to the access standard identifier, and the capability field corresponding to the access system identifier. If the access system identifier and the capability field corresponding to the access system identifier are not included in the capability list, the base station determines that the terminal does not support the access system corresponding to the access system identifier.
  • the base station can determine the access system capability of the terminal by using any of the access system identifiers in the capability standard list, and determining, by the base station, the terminal support.
  • the access system identifies an access system corresponding to the access system.
  • the base station determines that the terminal does not support the access system corresponding to the access standard identifier.
  • the base station may notify the core network device of the terminal capability information of the terminal by using the terminal capability indication message.
  • the core network device may save the terminal capability information of the terminal, and when the terminal establishes an RRC connection with the base station, send the terminal capability information of the terminal to the initial context setting request.
  • a base station that establishes an RRC connection with the terminal Therefore, when the base station that establishes an RRC connection with the terminal receives the terminal capability information of the terminal sent by the core network device, the access system capability of the terminal can be obtained.
  • the access system capability of the terminal can be forwarded to the target base station, so that the target base station is When the access system capability of the terminal forwarded by the source base station is received, the access system capability of the terminal can be obtained.
  • the embodiment of the present invention provides a wireless communication device, specifically for implementing the method described in the embodiments described in FIG. 2 to FIG. 5, which may be a terminal device itself, or a chip or a chipset or a chip in the terminal device.
  • the device is configured as shown in FIG. 6 and includes a physical interface such as a communication interface 601 and a processor 602.
  • the processor 602 can be a central processing unit (CPU). , a microprocessor, an application specific integrated circuit, a programmable logic circuit, a large scale integrated circuit, or a digital processing unit, and the like.
  • the communication interface 601 is used for data transmission and reception by the terminal device and other devices, and the communication interface 601 can be a radio frequency transceiver, and is mainly used for modulating the baseband signal processed by the processor 602 into a high frequency wireless signal transmission. Going out, the received high frequency wireless signal is processed into a baseband data signal transmission processor 602 for processing.
  • the communication interface 601 can also be a physical interface between the processor and a radio frequency transceiver in the terminal device.
  • the apparatus may also include a memory 603 for storing programs executed by the processor 602, and of course may store some other data and the like required by the terminal device.
  • the memory 603 may be a volatile memory such as a random-access memory (RAM).
  • the memory 603 may also be a non-volatile memory such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid state hard disk (solid).
  • ROM read-only memory
  • HDD hard disk drive
  • solid state hard disk solid
  • a -state drive (SSD), or memory 603 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 603 may be a combination of the above memories.
  • connection medium between the processor 602, the memory 603, and the communication interface 601 is not limited in the embodiment of the present application.
  • only the memory 603, the processor 602, and the communication interface 601 are connected by a bus 604 in FIG. 6 as an example.
  • the bus is indicated by a thick line in FIG. 6, and the connection manner between other components is only It is intended to be illustrative and not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 6, but it does not mean that there is only one bus or one type of bus.
  • the processor 602 may be dedicated hardware or a processor running software. When the processor 602 can run the software, the processor 602 reads the instructions stored in the memory 603 and, under the driving of the instructions, executes the operations involved in the previous embodiment. method.
  • the communication interface 601 is configured to receive a terminal capability request message from the network device, where the terminal capability request message is used to indicate that the UE reports the access capability.
  • the network device can be a base station.
  • the processor 602 is configured to construct terminal capability information, where the terminal capability information carries an access system identifier that is not supported by the terminal.
  • the communication interface 601 is further configured to send the terminal capability information configured by the processor 602 to the network device.
  • the terminal capability information includes a capability system list, where the capability system list includes at least one supported access system identifier and a corresponding capability field, and at least one unsupported access system identifier, optionally
  • the capability field corresponding to an access system identifier is used to indicate the access capability of the terminal to access the access system corresponding to any one of the access system identifiers.
  • the terminal capability request message carries at least one access system identifier. If the terminal supports the first access system corresponding to the first access system identifier, the capability system list includes the first access system identifier and the corresponding capability field. If the terminal does not support the first access system, the capability system list includes the first access system identifier, and does not include the capability field corresponding to the first access system identifier.
  • the first access system identifier is any access system identifier in the access system identifier carried by the terminal capability request message.
  • the processor 602 may be specifically configured to: set the first access system identifier and the corresponding field to be filled in the capability system list. If the wireless communication device supports the first access system, the capability field corresponding to the first access system identifier is filled in the corresponding to-be-filled field.
  • the terminal capability request message carries at least one access system identifier.
  • the terminal capability information includes a request list and a capability system list, where the request list includes an access system identifier carried by the terminal capability request message, where the capability system list includes at least one supported access system identifier and corresponding Capability field.
  • the base station may determine, according to the access system identifier included in the capability standard list, the access system supported by the terminal, and determine, according to the access system identifier included in the request list and not included in the capability standard list, the terminal does not support the connection. Into the system, so that the access system capability of the terminal can be clearly known.
  • the request list includes a second access standard identifier. If the terminal supports the second access system corresponding to the second access system identifier, the capability system list includes the second access system identifier and the corresponding capability field, where the second access standard identifier is Any access system identifier in the access system identifier carried by the terminal capability request message.
  • the processor 602 may be specifically configured to: fill the request list with an access system identifier carried by the terminal capability request message. If the wireless communication device supports the second access system, setting the second access standard identifier and the corresponding field to be filled in the capability formula list, and filling the corresponding field to be filled The second access system identifies a corresponding capability field.
  • the terminal capability information carrying capability system list and the unsupported capability system list where the capability system list includes at least one supported access system identifier and a corresponding capability field.
  • the unsupported capability system list includes at least one unsupported access system identifier.
  • the base station may determine the access standard supported by the terminal according to the access system identifier included in the capability standard list, and determine the access system that the terminal does not support according to the access system identifier included in the unsupported capability standard list, thereby making it clear Know the access system capabilities of the terminal.
  • the capability system list includes the third access system identifier and the corresponding capability field, where The third access system identifier is any access system identifier in the access system identifier carried by the terminal capability request message. If the terminal does not support the third access system, the third access standard identifier is included in the unsupported capability list.
  • the processor 602 may be specifically configured to: if the wireless communication device supports the third access system, set the third access standard identifier and corresponding to be filled in the capability standard list. a field, and populating, in the corresponding to-be-filled field, a capability field corresponding to the third access standard identifier. And if the wireless communication device does not support the third access system, setting the third access standard identifier in the unsupported capability formula list.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the corresponding device may include multiple functional modules, and each functional module may include software, hardware or a combination thereof.
  • the device is as shown in Fig. 7, which can be placed in the terminal device.
  • the receiving module 701 is configured to receive a terminal capability request message from the network device, where the terminal capability request message is used to indicate that the UE reports the access capability.
  • the constructing module 702 is configured to construct terminal capability information, where the terminal capability information carries an access system identifier that is not supported by the terminal.
  • the sending module 703 is configured to send the terminal capability information configured by the constructing module 702 to the network device.
  • the terminal capability information includes a capability system list, where the capability system list includes at least one supported access system identifier and a corresponding capability field, and at least one unsupported access system identifier, optionally
  • the capability field corresponding to an access system identifier is used to indicate the access capability of the terminal to access the access system corresponding to any one of the access system identifiers.
  • the terminal capability request message carries at least one access system identifier. If the terminal supports the first access system corresponding to the first access system identifier, the capability system list includes the first access system identifier and the corresponding capability field. If the terminal does not support the first access system, the capability system list includes the first access system identifier, and does not include the capability field corresponding to the first access system identifier.
  • the first access system identifier is any access system identifier in the access system identifier carried by the terminal capability request message.
  • the constructing module 702 may be specifically configured to: set the first access system identifier and the corresponding field to be filled in the capability system list. If the wireless communication device supports the first access system, the capability field corresponding to the first access system identifier is filled in the corresponding to-be-filled field.
  • the terminal capability request message carries at least one access system identifier.
  • the terminal capability information includes a request list and a capability system list, where the request list includes an access system identifier carried by the terminal capability request message, where the capability system list includes at least one supported access system identifier and corresponding Capability field.
  • the base station may determine, according to the access system identifier included in the capability standard list, the access system supported by the terminal, and determine, according to the access system identifier included in the request list and not included in the capability standard list, the terminal does not support the connection. Into the system, so that the access system capability of the terminal can be clearly known.
  • the request list includes a second access standard identifier. If the terminal supports the second access system corresponding to the second access system identifier, the capability system list includes the second access system identifier and the corresponding capability field, where the second access standard identifier is Any access system identifier in the access system identifier carried by the terminal capability request message.
  • the constructing module 702 may be specifically configured to: fill the request list with an access system identifier carried by the terminal capability request message. If the wireless communication device supports the second access system, setting the second access standard identifier and the corresponding field to be filled in the capability formula list, and filling the corresponding field to be filled The second access system identifies a corresponding capability field.
  • the terminal capability information carrying capability system list and the unsupported capability system list where the capability system list includes at least one supported access system identifier and a corresponding capability field.
  • the unsupported capability system list includes at least one unsupported access system identifier.
  • the base station may determine the access standard supported by the terminal according to the access system identifier included in the capability standard list, and determine the access system that the terminal does not support according to the access system identifier included in the unsupported capability standard list, thereby making it clear Know the access system capabilities of the terminal.
  • the capability system list includes the third access system identifier and the corresponding capability field, where The third access system identifier is any access system identifier in the access system identifier carried by the terminal capability request message. If the terminal does not support the third access system, the third access standard identifier is included in the unsupported capability list.
  • the constructing module 702 may be specifically configured to: if the wireless communication device supports the third access system, set the third access standard identifier and corresponding to be filled in the capability standard list. a field, and populating, in the corresponding to-be-filled field, a capability field corresponding to the third access standard identifier. And if the wireless communication device does not support the third access system, setting the third access standard identifier in the unsupported capability formula list.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the building block 702 can be the processor 602.
  • the receiving module 701 and the transmitting module 703 may be the communication interface 601.
  • the embodiment of the present invention provides a wireless communication device, which is specifically used to implement the method described in the embodiments of FIG. 2 to FIG. 5, where the device may be a source base station that establishes an RRC connection with the terminal, or may perform a cell handover when the terminal performs cell handover.
  • the destination base station for access may be the base station itself, or may be part of a chip or chipset or chip in the base station for performing related method functions.
  • the structure of the device is as shown in FIG. 8, and includes a physical interface such as a communication interface 801 and a processor 802.
  • the processor 802 can be a CPU, a microprocessor, an application specific integrated circuit, a programmable logic circuit, a large scale integrated circuit, or a digital processing unit or the like.
  • the communication interface 801 is used for data transmission and reception by the terminal device and other devices, and the communication interface 801 can be a radio frequency transceiver, which is mainly used for modulating the baseband signal processed by the processor 802 into a high frequency wireless signal. And receiving the received high frequency wireless signal into a baseband data signal transmission processor 802 for processing.
  • the communication interface 801 can also be a physical interface between the processor and a radio frequency transceiver in the terminal device.
  • the apparatus may also include a memory 803 for storing programs executed by the processor 802, and of course may store some other data and the like required by the terminal device.
  • the memory 803 can be a volatile memory such as a RAM.
  • the memory 803 can also be a non-volatile memory such as a ROM, flash memory, HDD or SSD, or the memory 803 can be any other program that can be used to carry or store desired program code in the form of an instruction or data structure and can be accessed by a computer. Medium, but not limited to this.
  • the memory 803 may be a combination of the above memories.
  • connection medium between the processor 802, the memory 803, and the communication interface 801 is not limited in the embodiment of the present application.
  • only the memory 803, the processor 802, and the communication interface 801 are connected by a bus 804 in FIG. 8 as an example.
  • the bus is indicated by a thick line in FIG. 8 and the connection manner between other components is only It is intended to be illustrative and not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 8, but it does not mean that there is only one bus or one type of bus.
  • the processor 802 can be dedicated hardware or a processor running software. When the processor 802 can run software, the processor 802 reads the instructions stored in the memory 803 and, under the driving of the instructions, executes the operations involved in the previous embodiment. method.
  • the communication interface 801 is configured to receive terminal capability information, where the terminal capability information carries an access system identifier that is not supported by the terminal, the terminal capability information is from the terminal, or the terminal capability information is from the second network.
  • the device, the n is an integer greater than 0, and the second network device may be another base station or a core network device.
  • the processor 802 is configured to determine an access system capability of the terminal according to the terminal capability information received by the communication interface 801.
  • the terminal capability information may be the terminal capability information described in FIG. 2 to FIG. 5.
  • the terminal capability information is sent from the terminal, and the communication interface 801 is further configured to: before receiving the terminal capability information of the terminal, send a terminal capability request message to the terminal, where the terminal capability request message is used to indicate The UE reports the access standard capability.
  • the communication interface 801 is further configured to: after receiving the terminal capability information of the terminal, send the terminal capability information to the third network device.
  • the third network device may be another base station or a core network device.
  • the processor 802 may be specifically configured to: if the capability system list includes a capability field corresponding to the second access system identifier, determine that the terminal supports the second access system Identifying a corresponding second access system, where the second access system identifier is any access system identifier included in the capability system list. Alternatively, if the capability field corresponding to the second access system identifier is not included in the capability list, it is determined that the terminal does not support the second access system.
  • the processor 802 may be specifically configured to: if the capability system list includes a fourth access system identifier and a capability field corresponding to the fourth access system identifier, determine the location The terminal supports the fourth access system corresponding to the fourth access system identifier, and the fourth access system identifier is any access system identifier included in the request list. Alternatively, if the capability model list does not include the capability information field corresponding to the fourth access system identifier and the fourth access system identifier, determining that the terminal does not support the fourth access system.
  • the processor 802 may be specifically configured to: determine that the terminal supports an access system corresponding to the sixth access standard identifier, where the sixth access system identifier is the capability standard Any access system identifier in the list. Or determining that the terminal does not support the access system corresponding to the seventh access system identifier, where the seventh access system identifier is any access system identifier in the unsupported capability system list.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the corresponding device may include multiple functional modules, and each functional module may include software, hardware or a combination thereof.
  • the device is shown in Figure 9, which can be placed in the base station.
  • the receiving module 901 is configured to receive terminal capability information, where the terminal capability information carries an access system identifier that is not supported by the terminal, the terminal capability information is from the terminal, or the terminal capability information is from the second network device.
  • the second network device may be another base station, or a core network device, where n is an integer greater than 0.
  • the determining module 902 is configured to determine an access system capability of the terminal according to the terminal capability information received by the receiving module 901.
  • the base station may further include a sending module 903, configured to send a terminal capability request message to the terminal, the terminal capability, before the receiving module 901 receives the terminal capability information of the terminal.
  • the request message is used to indicate that the UE reports the access standard capability.
  • the sending module 903 is further configured to: after the receiving module 901 receives the terminal capability information of the terminal, send the terminal capability information to the third network device, where the third network device may be other
  • the base station can also be a core network device.
  • the determining module 902 may be specifically configured to: if the capability system list includes a capability field corresponding to the second access system identifier, determine that the terminal supports the second access system Identifying a corresponding second access system, where the second access system identifier is any access system identifier included in the capability system list. Alternatively, if the capability field corresponding to the second access system identifier is not included in the capability list, it is determined that the terminal does not support the second access system.
  • the determining module 902 may be specifically configured to: if the capability system list includes a fourth access system identifier and a capability field corresponding to the fourth access system identifier, determine the location The terminal supports the fourth access system corresponding to the fourth access system identifier, and the fourth access system identifier is any access system identifier included in the request list. Alternatively, if the capability model list does not include the capability information field corresponding to the fourth access system identifier and the fourth access system identifier, determining that the terminal does not support the fourth access system.
  • the determining module 902 may be specifically configured to: determine that the terminal supports an access system corresponding to the sixth access standard identifier, where the sixth access system identifier is the capability standard Any access system identifier in the list. Or determining that the terminal does not support the access system corresponding to the seventh access system identifier, where the seventh access system identifier is any access system identifier in the unsupported capability system list.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules.
  • the determining module 902 can be the processor 802.
  • the receiving module 901 and the transmitting module 903 may be a communication interface 801.
  • the embodiment of the invention provides a wireless communication device, which is specifically used to implement the method described in the embodiments of FIG. 2 to FIG. 5, which may be a core network device itself, or a chip or a chipset in a core network device. Or a part of the chip for performing related method functions, the structure of the device is as shown in FIG. 10, and includes a physical device such as a communication interface 1001 and a processor 1002, wherein the processor 1002 may be a CPU, a microprocessor, or an application specific integrated circuit. , programmable logic circuits, large scale integrated circuits, or as digital processing units, and the like.
  • the communication interface 1001 is used for the terminal device and other devices to perform data transmission and reception.
  • the communication interface 1001 may be a radio frequency communication interface device, and is mainly used for modulating the baseband signal processed by the processor 1002 into a high frequency wireless device. The signal is transmitted and the received high frequency wireless signal is processed into a baseband data signal transmission processor 1002 for processing.
  • the communication interface 601 can also be a physical interface between the processor and a radio frequency transceiver in the terminal device.
  • the apparatus may further include a memory 1003 for storing a program executed by the processor 1002, and of course may store some other data and the like required by the terminal device.
  • the memory 1003 may be a volatile memory such as a RAM.
  • the memory 1003 may also be a non-volatile memory such as a ROM, flash memory, HDD or SSD, or the memory 1003 is any other device that can be used to carry or store desired program code in the form of an instruction or data structure and can be accessed by a computer. Medium, but not limited to this.
  • the memory 1003 may be a combination of the above memories.
  • the specific connection medium between the processor 1002, the memory 1003, and the communication interface 1001 is not limited in the embodiment of the present application.
  • only the memory 1003, the processor 1002, and the communication interface 1001 are connected by a bus 1004 in FIG. 10 as an example.
  • the bus is indicated by a thick line in FIG. 10, and the connection manner between other components is only It is intended to be illustrative and not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • the processor 1002 may be dedicated hardware or a processor running software. When the processor 1002 can run software, the processor 1002 reads the instructions stored in the memory 1003 and, under the driving of the instructions, executes the operations involved in the previous embodiment. method.
  • the communication interface 1001 is configured to receive terminal capability information from the second network device, where the terminal capability information carries an access system identifier that is not supported by the terminal in the access system identifier carried by the terminal capability request message, and The access system identifier supported by the terminal in the access system identifier carried by the terminal capability request message.
  • the second network device can be a base station.
  • the processor 1002 is configured to save the terminal capability information received by the communication interface 1001 in the memory 1003, and send the terminal capability information to the second network device by using the communication interface 1001.
  • the terminal capability information may be the terminal capability information described in FIG. 2 to FIG. 5.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the corresponding device may include multiple functional modules, and each functional module may include software, hardware or a combination thereof.
  • the device is shown in Figure 11, which can be placed in the core network device.
  • the receiving module 1101 is configured to receive terminal capability information from other network devices, where the other network device may be a base station, where the terminal capability information carries an access system identifier carried by the terminal capability request message, and the terminal does not support An access system identifier, and an access system identifier supported by the terminal in the access system identifier carried in the terminal capability request message.
  • the saving module 1102 is configured to save the terminal capability information received by the receiving module 1101.
  • the sending module 1103 is configured to send the terminal capability information saved by the saving module 1102 to the second network device.
  • each functional module in each embodiment of the present application may be integrated into one processing. In the device, it can also be physically existed alone, or two or more modules can be integrated into one module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. Wherein, when the integrated module can be implemented in the form of hardware, the saving module 1102 can be the processor 1002.
  • the receiving module 1101 and the transmitting module 1103 may be the communication interface 1001.
  • the embodiment of the invention further provides a computer readable storage medium for storing computer software instructions required to execute the above-mentioned processor, which comprises a program for executing the above-mentioned processor.
  • Embodiments of the present application provide a computer program product comprising instructions that, when run on a computer, cause the computer to perform the wireless communication method described in Figures 2-5.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

一种无线通信方法及设备,用于解决基站可能无法准确获知UE的接入制式能力的问题。所述方法具体包括:终端接收网络设备发送的终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力。所述终端向所述网络设备发送终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识。

Description

一种无线通信方法及设备 技术领域
本申请涉及通信技术领域,尤其涉及一种无线通信方法及设备。
背景技术
在移动通信系统中,基站在为用户设备(user equipment,UE)分配无线资源时,首先需要了解UE的接入制式能力,UE的接入制式能力指UE能够支持的接入制式,以及UE接入该接入制式的接入能力。接入制式包括通用地面无线接入(universal terrestrial radio access,UTRA)、演进的UTRA(E-UTRA)、新无线技术(new radio,NR)等等。之后基站基于UE的接入制式能力为UE分配无线资源,从而最大化无线资源的使用效率。
目前基站获取UE的接入制式能力的途径,通常有:当UE与基站完成无线资源控制(Radio Resource Control,RRC)连接后,如果核心网保存有该UE的接入制式能力,核心网将该UE的接入制式能力通过初始上下文设置请求(Initial Context Setup Request)发送给基站,从而基站获取了该UE的接入制式能力。如果核心网没有保存该UE的接入制式能力,则基站通过向UE发送终端能力请求(UE Capability Request)消息指示UE上报自身的接入制式能力。或者,UE在进行小区切换时,基站接收该UE的源基站转发的该UE的接入制式能力。
然而,基站在接收到核心网或者其他基站转发的某UE的接入制式能力时,可能无法准确获知UE的所有接入制式能力。例如,核心网或者其他基站转发的某UE的接入制式能力中仅包含UTRA的接入制式标识和相应的能力字段,这时基站可能无法准确获知该UE是否还支持其他接入制式,因此,基站可能无法准确获知UE的接入制式能力。
发明内容
本申请实施例提供了一种无线通信方法及设备,用于解决基站可能无法准确获知UE的接入制式能力的问题。
第一方面,本申请实施例提供了一种无线通信方法,包括:终端接收网络设备发送的终端能力请求消息,并向网络设备发送终端能力信息,其中网络设备可以为基站。终端能力请求消息用于指示UE上报接入制式能力。所述终端能力信息中携带所述终端不支持的接入制式标识。本申请实施例中通过终端在终端能力信息中增加终端不支持的接入制式标识,从而基站获取到终端的接入制式能力时,除了可以明确获知终端支持的接入制式,还可以获知终端不支持的接入制式,从而可以降低基站再次发起能力查询流程的几率,进而可以减少空口信令的开销,降低终端接入和业务启动的时延。
在一种可能的设计中,终端能力信息中可以携带终端能力请求消息携带的至少一个接入制式标识中终端所有不支持的接入制式标识,也可以携带终端能力请求消息携带的至少一个接入制式标识中终端部分不支持的接入制式标识。
在一种可能的设计中,所述终端能力信息包括能力制式列表,所述能力制式列表包括至少一个支持的接入制式标识以及对应的能力字段、至少一个不支持的接入制式标识,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识 所对应接入制式的接入能力。上述设计中,基站可以通过判断终端能力信息中是否携带某接入制式标识对应的能力字段,来确定终端是否支持该接入制式标识对应的接入制式,从而可以明确获知该终端的接入制式能力。
在一种可能的设计中,所述终端能力请求消息携带至少一个接入制式标识。若所述终端支持第一接入制式标识对应的第一接入制式,则所述能力制式列表中包括所述第一接入制式标识以及对应的能力字段。若所述终端不支持所述第一接入制式,则所述能力制式列表中包括所述第一接入制式标识,且未包括所述第一接入制式标识对应的能力字段。所述第一接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。上述设计中,通过将能力字段设置成可选的,终端针对支持的接入制式,可以在终端能力信息中携带该接入制式的标识以及能力字段,针对不支持的接入制式,在终端能力信息中携带该接入制式的标识,不携带能力字段,使得基站可以通过判断终端能力信息中是否携带某接入制式标识对应的能力字段确定终端是否支持该接入制式标识对应的接入制式,从而可以明确获知该终端的接入制式能力。
在一种可能的设计中,所述终端通过如下方式构造所述终端能力信息:所述终端在所述能力制式列表中设置所述第一接入制式标识以及对应的待填充字段。若所述终端支持所述第一接入制式标识对应的接入制式,则所述终端在所述对应的待填充字段中填充所述第一接入制式标识对应的能力字段。上述设计中,基站可以通过判断终端能力信息中是否携带某接入制式标识对应的能力字段,来确定终端是否支持该接入制式标识对应的接入制式,从而可以明确获知该终端的接入制式能力。
在一种可能的设计中,所述终端能力请求消息携带至少一个接入制式标识。所述终端能力信息中携带请求列表以及能力制式列表,所述请求列表包括所述终端能力请求消息携带的接入制式标识,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段。上述设计中,基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据请求列表中包括的、且能力制式列表中未包括的接入制式标识确定终端不支持的接入制式,从而可以明确获知该终端的接入制式能力。
在一种可能的设计中,所述请求列表中包括第二接入制式标识。若所述终端支持第二接入制式标识对应的第二接入制式,则所述能力制式列表中包括所述第二接入制式标识以及对应的能力字段,所述第二接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。上述设计中,终端通过在终端能力信息中增加请求列表,从而基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据请求列表中包括的、且能力制式列表中未包括的接入制式标识确定终端不支持的接入制式。
在一种可能的设计中,所述终端通过如下方式构造所述终端能力信息:所述终端在所述请求列表中填充所述终端能力请求消息携带的接入制式标识。若所述终端支持所述第二接入制式,则所述终端在所述能力制式列表中设置所述第二接入制式标识以及对应的待填充字段,并在所述对应的待填充字段中填充所述第二接入制式标识对应的能力字段。上述设计中,基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据请求列表中包括的、且能力制式列表中未包括的接入制式标识确定终端不支持的接入制式,从而可以明确获知该终端的接入制式能力。
在一种可能的设计中,所述终端能力信息携带能力制式列表以及不支持的能力制式列表,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段。所述不 支持的能力制式列表中包括至少一个不支持的接入制式标识。上述设计中,基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据不支持的能力制式列表包括的接入制式标识确定终端不支持的接入制式,从而可以明确获知该终端的接入制式能力。
在一种可能的设计中,若所述终端支持第三接入制式标识对应的第三接入制式,则所述能力制式列表中包括所述第三接入制式标识以及对应的能力字段,若所述终端不支持所述第三接入制式,则所述不支持的能力制式列表中包括所述第三接入制式标识。所述第三接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。上述设计中,终端通过在终端能力信息中增加不支持的能力制式列表,从而基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据不支持的能力制式列表包括的接入制式标识确定终端不支持的接入制式。
在一种可能的设计中,所述终端通过如下方式构造所述终端能力信息:若所述终端支持所述第三接入制式,则所述终端在所述能力制式列表中设置所述第三接入制式标识以及对应的待填充字段,并在所述对应的待填充字段中填充所述第三接入制式标识对应的能力字段。若所述终端不支持所述第三接入制式,则所述终端在所述不支持的能力制式列表中设置所述第三接入制式标识。上述设计中,基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据不支持的能力制式列表包括的接入制式标识确定终端不支持的接入制式,从而可以明确获知该终端的接入制式能力。
第二方面,本申请实施例提供了一种无线通信方法,包括:第一网络设备向终端发送终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力。所述第一网络设备接收终端上报的终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识,终端能力信息可以为上述第一方面或上述第一方面的任意一种设计中所述的终端能力信息。其中,第一网络设备可以为与终端建立RRC连接的基站。本申请实施例中通过终端在终端能力信息中增加终端不支持的接入制式标识,从而基站获取到终端的接入制式能力时,除了可以明确获知终端支持的接入制式,还可以获知终端不支持的接入制式,从而可以降低基站再次发起能力查询流程的几率,进而可以减少空口信令的开销,降低终端接入和业务启动的时延。
在一种可能的设计中,所述第一网络设备根据所述终端能力信息确定所述终端的接入制式能力。或者,所述第一网络设备在与所述终端建立RRC连接时,将所述终端能力信息转发给第二网络设备,以使所述第二网络设备保存所述终端的接入制式能力,其中,第二网络设备可以为核心网设备。或者,所述第一网络设备在将所述终端切换到第三网络设备时,将所述终端能力信息转发给第三网络设备,以使所述第三网络设备确定所述终端的接入制式能力,其中,第三网络设备可以为终端进行小区切换时要接入的目标基站。上述设计中,基站在获取终端的接入制式消息后,还可以将该终端的接入制式能力通知给核心网,也可以在将该终端切换到其它基站时,将该终端的接入制式能力转发给其它基站。
在一种可能的设计中,所述第一网络设备根据所述终端能力信息确定所述终端的接入制式能力,包括:若所述能力制式列表中包括第二接入制式标识对应的能力字段,所述第一网络设备确定所述终端支持所述第二接入制式标识对应的第二接入制式,所述第二接入制式标识为所述能力制式列表中包括的任一接入制式标识。或者,若所述能力制式列表中未包括所述第二接入制式标识对应的能力字段,所述第一网络设备确定所述终端不支持所 述第二接入制式。上述设计中,基站可以通过判断终端能力信息中是否携带某接入制式标识对应的能力字段确定终端是否支持该接入制式标识对应的接入制式,从而可以获知该终端的接入制式能力。
在一种可能的设计中,所述第一网络设备根据所述终端能力信息确定所述终端的接入制式能力,包括:若所述能力制式列表中包括第四接入制式标识以及所述第四接入制式标识对应的能力字段,所述第一网络设备确定所述终端支持所述第四接入制式标识对应的第四接入制式,所述第四接入制式标识为所述请求列表中包括的任一接入制式标识。或者,若所述能力制式列表中未包括所述第四接入制式标识以及所述第四接入制式标识对应的能力字段,所述第一网络设备确定所述终端不支持所述第四接入制式。上述设计中,终端通过在终端能力信息中增加请求列表,从而基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据请求列表中包括的、且能力制式列表中未包括的接入制式标识确定终端不支持的接入制式。
在一种可能的设计中,所述第一网络设备根据所述终端能力信息确定所述终端的接入制式能力,包括:所述第一网络设备确定所述终端支持第六接入制式标识对应的接入制式,所述第六接入制式标识为所述能力制式列表中的任一接入制式标识。或者,所述第一网络设备确定所述终端不支持第七接入制式标识对应的接入制式,所述第七接入制式标识为所述不支持的能力制式列表中的任一接入制式标识。上述设计中,终端通过在终端能力信息中增加不支持的能力制式列表,从而基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据不支持的能力制式列表包括的接入制式标识确定终端不支持的接入制式。
第三方面,本申请实施例提供了一种无线通信方法,包括:第一网络设备接收并保存第二网络设备发送的终端能力信息,所述终端能力信息中携带终端不支持的接入制式标识。所述第一网络设备向第三网络设备发送所述终端能力信息。其中,第一网络设备可以为核心网设备,第二网络设备可以为与终端建立RRC连接的基站。终端能力信息可以为上述第一方面或上述第一方面的任意一种设计中所述的终端能力信息。本申请实施例中,核心网设备保存的某终端的接入制式能力中包括该终端不支持的接入制式标识,以及支持的接入制式标识,从而所述核心网设备可以向基站转发包括不支持的接入制式标识,以及支持的接入制式标识的接入制式能力,从而基站在接收到核心网转发的终端的接入制式能力时,除了可以明确获知终端支持的接入制式,还可以获知终端不支持的接入制式,从而可以降低基站再次发起能力查询流程的几率,进而可以减少空口信令的开销,降低终端接入和业务启动的时延。
第四方面,本申请实施例提供了一种无线通信方法,包括:第一网络设备接收第二网络设备发送的终端能力信息,所述终端能力信息中携带终端不支持的接入制式标识。所述第一网络设备根据所述终端能力信息确定所述终端的接入制式能力。第一网络设备可以为核心网设备,也可以为终端在进行小区切换之前接入的基站。终端能力信息可以为上述第一方面或上述第一方面的任意一种设计中所述的终端能力信息。其中,所述第一网络设备根据所述终端能力信息确定所述终端的接入制式能力的方法可以为上述第二方面或上述第二方面的任意一种设计中所述的方法。本申请实施例中,核心网设备保存的某终端的接入制式能力中包括该终端不支持的接入制式标识,以及支持的接入制式标识,从而所述核心网设备可以向基站转发包括不支持的接入制式标识,以及支持的接入制式标识的接入制 式能力,从而基站在接收到其他基站转发的终端的接入制式能力时,除了可以明确获知终端支持的接入制式,还可以获知终端不支持的接入制式,从而可以降低基站再次发起能力查询流程的几率,进而可以减少空口信令的开销,降低终端接入和业务启动的时延。
第五方面,本申请实施例中还提供一种终端,包括:接收模块,用于接收来自网络设备的终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力。构造模块,用于构造终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识。发送模块,用于向所述网络设备发送所述构造模块构造的所述终端能力信息。其中,终端能力信息可以为上述第一方面或上述第一方面的任意一种设计中所述的终端能力信息。
第六方面,本申请实施例中还提供一种第一网络设备,所述第一网络设备可以为与终端建立RRC连接的源基站,下面以第一网络设备为源基站为例进行说明。源基站包括:发送模块,用于向终端发送终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力。接收模块,用于接收终端上报的终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识。其中,终端能力信息可以为上述第一方面或上述第一方面的任意一种设计中所述的终端能力信息。
在一种可能的设计中,基站还包括确定模块。确定模块,用于根据所述终端能力信息确定所述终端的接入制式能力。
在一种可能的设计中,所述发送模块,还用于在与所述终端建立RRC连接时,将所述终端能力信息转发给第二网络设备,以使所述第二网络设备保存所述终端的接入制式能力。
在一种可能的设计中,所述发送模块,还用于在将所述终端切换到第三网络设备时,将所述终端能力信息转发给所述第三网络设备,以使所述第三网络设备确定所述终端的接入制式能力。
在一种可能的设计中,所述确定模块,具体用于:若所述能力制式列表中包括第二接入制式标识对应的能力字段,确定所述终端支持所述第二接入制式标识对应的第二接入制式,所述第二接入制式标识为所述能力制式列表中包括的任一接入制式标识。或者,若所述能力制式列表中未包括所述第二接入制式标识对应的能力字段,确定所述终端不支持所述第二接入制式。
在一种可能的设计中,所述确定模块,具体用于:若所述能力制式列表中包括第四接入制式标识以及所述第四接入制式标识对应的能力字段,确定所述终端支持所述第四接入制式标识对应的第四接入制式,所述第四接入制式标识为所述请求列表中包括的任一接入制式标识。或者,若所述能力制式列表中未包括所述第四接入制式标识以及所述第四接入制式标识对应的能力字段,确定所述终端不支持所述第四接入制式。
在一种可能的设计中,所述确定模块,具体用于:确定所述终端支持第六接入制式标识对应的接入制式,所述第六接入制式标识为所述能力制式列表中的任一接入制式标识。或者,确定所述终端不支持第七接入制式标识对应的接入制式,所述第七接入制式标识为所述不支持的能力制式列表中的任一接入制式标识。
第七方面,本申请实施例中还提供一种第二网络设备,该第二网络设备可以为核心网设备,下面以第二网络设备为核心网设备为例进行说明,核心网设备包括:接收模块,用于接收来自基站的终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识。保存模块,用于将所述接收模块接收的所述终端能力信息进行保存。发送模块,用于 向第二网络设备发送所述保存模块保存的终端能力信息。
第八方面,本申请实施例中还提供一种第三网络设备,该第三网络设备可以为终端进行小区切换时接入的目标基站,下面以第三网络设备为目的基站为例进行说明,目的基站包括:接收模块,用于接收第二网络设备发送的终端能力信息,所述终端能力信息中携带终端不支持的接入制式标识。确定模块,用于根据所述终端能力信息确定所述终端的接入制式能力。所述确定模块可以为上述第六方面或第六方面的任意一种设计中所述的确定模块。
第九方面,本申请实施例中还提供了一种无线通信装置,该装置包括通信接口、处理器和存储器,所述通信接口用于收发信号,所述存储器用于存储软件程序,所述处理器用于读取所述存储器中存储的软件程序并实现第一方面至第四方面中任一方面或任一方面的任意一种设计提供的方法。
第十方面,本申请实施例中还提供一种计算机存储介质,该存储介质中存储软件程序,该软件程序在被一个或多个处理器读取并执行时可实现第一方面至第四方面中任一方面或任一方面的任意一种设计提供的方法。
第十一方面,本申请实施例提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行第一方面至第四方面中任一方面或任一方面的任意一种设计所述的方法。
第十二方面,本申请实施例提供了一种芯片,所述芯片与存储器相连,用于读取并执行所述存储器中存储的软件程序,以实现上述可实现第一方面至第四方面中任一方面或任一方面的任意一种设计提供的方法。
附图说明
图1为本申请实施例提供的一种通信系统的架构示意图;
图2为本申请实施例提供的一种基站获取终端的接入制式能力的流程示意图;
图3为本申请实施例提供的另一种基站获取终端的接入制式能力的流程示意图;
图4为本申请实施例提供的另一种基站获取终端的接入制式能力的流程示意图;
图5为本申请实施例提供的一种无线通信方法的流程示意图;
图6为本申请实施例提供的一种无线通信装置的结构示意图;
图7为本申请实施例提供的一种无线通信装置的结构示意图;
图8为本申请实施例提供的一种无线通信装置的结构示意图;
图9为本申请实施例提供的一种无线通信装置的结构示意图;
图10为本申请实施例提供的一种无线通信装置的结构示意图;
图11为本申请实施例提供的一种无线通信装置的结构示意图。
具体实施方式
下面将结合附图对本申请实施例作进一步地详细描述。
本申请提供的无线通信方法可以应用于通信系统中。该通信系统的架构可以如图1所示,包括基站101以及终端设备102,还可以包括核心网设备103以及基站104,其中,基站104可以为终端设备102进行小区切换后接入的基站。本申请实施例涉及的通信系统 可以是各类通信系统,例如,可以是长期演进(long term evolution,LTE),也可以是第五代(5G)通信系统,也可以为通用地面无线接入(universal terrestrial radio access,UTRA)、演进的UTRA(E-UTRAN)、新无线技术(new radio,NR)、GSM/EDGE无线接入网-电路交换域(GSM EDGE radio access network-circuit switched,GERAN-CS)、GSM/EDGE无线接入网-数据交换域(GSM EDGE radio access network–packet switched,GERAN-PS)、码分多址(code division multiple access,CDMA)2000-1XRTT、和多无线接入技术双连接(Multi-RAT Dual-Connectivity,MR-DC)等,还可以是多种通信系统的混合架构,如LTE与5G混合架构等。
其中,基站101、基站104,可以是普通的基站(如Node B或eNB),可以是新无线控制器(New Radio controller,NR controller),可以是5G系统中的gNode B(gNB),可以是集中式网元(Centralized Unit),可以是新无线基站,可以是射频拉远模块,可以是微基站,可以是中继(relay),可以是分布式网元(Distributed Unit),可以是接收点(Transmission Reception Point,TRP)或传输点(Transmission Point,TP)或者任何其它无线接入设备,但本申请实施例不限于此。
终端设备102,又称之为用户设备(User Equipment,UE),是一种向用户提供语音和/或数据连通性的设备,例如,具有无线连接功能的手持式设备、车载设备等。常见的终端例如包括:手机、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device,MID)、可穿戴设备,例如智能手表、智能手环、计步器等。
核心网设备103,可以是移动性管理实体(mobility management entity,MME),可以是业务网关(serving gateway,SGW),也可以是5G系统中的接入管理功能(Access and Management Function,AMF)等等,核心网设备可以提供进一步网络连接,例如电话网络和/或数据通信网络(例如Internet)。基站可以通过链路(例如S1接口)与核心网设备连接。
在移动通信系统中,UE接入各种接入制式下的接入能力与其软硬件配置相关。基站在为UE分配无线资源时,首先需要了解该UE的接入制式能力,UE的接入制式能力指UE能够支持的接入制式,以及UE接入该接入制式的接入能力。然后基于该UE的接入制式能力为该UE分配无线资源,从而最大化无线资源的使用效率。接入制式的类型包括UTRA、E-UTRAN、NR、GERAN-CS、GERAN-PS、CDMA2000-1XRTT、和MR-DC等。
当UE与基站完成无线资源控制(Radio Resource Control,RRC)连接后,如果核心网保存有该UE的接入制式能力,则将该UE的能力通过初始上下文设置请求(Initial Context Setup Request)发送给基站,如图2所示,从而基站获取了该UE的接入制式能力。
当UE与基站完成RRC连接后,如果核心网没有保存该UE的接入制式能力,即核心网发送给基站的Initial Context Setup Request消息中没有携带该UE的接入制式能力,那么基站就不能从核心网获得该UE的接入制式能力,这样基站需要发起能力查询流程,向UE查询各个接入制式的能力,如图3所示。
S301,基站向UE发送终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力。终端能力请求消息中可以携带至少一个接入制式标识,所述至少一个接入制式标识对应的接入制式即为UE需要上报的接入制式。比如,当UE驻留在E-UTRAN时,基站在终端能力请求消息中携带E-UTRAN、UTRA以及NR的标识,以指示UE上报 E-UTRAN、UTRA以及NR对应的接入能力。其中,各接入制式下对终端能力请求消息的命名不同,比如UTRA中,终端能力请求消息命名为UE Capability Request。E-UTRAN中,终端能力请求消息命名为UE Capability Enquiry。为了描述方便,本申请实施例中将基站发送的用于指示UE上报各个接入制式对应的接入能力的消息统一称为终端能力请求消息,在NR系统中可能将基站发送的用于指示UE上报各个接入制式对应的接入能力的消息命名为其他的名称,如XX。应理解,若该XX也可以实现本申请实施例中的终端能力请求消息所实现的功能,也可以将XX理解为本申请实施例中的终端能力请求消息。
S302,UE根据终端能力请求消息,组装终端能力信息,并向基站进行发送。该终端能力信息中包括UE需要上报的接入制式中该UE支持的接入制式的标识以及对应的接入能力。针对终端能力请求消息中携带的每个接入制式标识,如果UE支持该接入制式标识对应的接入制式,那么终端能力信息中包含该接入制式标识和相应的能力字段,能力字段用于表征UE接入该接入制式标识所对应接入制式的接入能力。如果UE不支持该接入制式,那么终端能力信息中不包含该接入制式标识,也不包含相应的能力字段。例如,基站在终端能力请求消息中指示UE上报UTRA、E-UTRAN、NR的接入能力。而UE支持UTRA、E-UTRAN,不支持NR,因此终端能力信息中携带UTRA的标识以及对应的能力字段,E-UTRAN的标识以及对应的能力字段。其中,各接入制式下对终端能力信息的命名不同,比如UTRA中,终端能力信息命名为UE Capability Response。E-UTRAN中,终端能力信息命名为UE Capability Information。为了描述方便,本申请实施例中将携带终端的接入制式能力的消息统一称为终端能力信息,在NR系统中可能将携带终端的接入制式能力的消息命名为其他的名称,如XX。应理解,若该XX也可以实现本申请实施例中的终端能力信息所实现的功能,也可以将XX理解为本申请实施例中的终端能力信息。
终端的接入制式能力可以基于ASN结构的代码携带在终端能力信息中,具体可以通过ASN结构的代码实现终端的接入制式能力:
Figure PCTCN2018081928-appb-000001
UE-CapabilityRAT-ContainerList为能力制式列表,其中包括终端支持的接入制式标识。UE-CapabilityRAT-Container用于指示支持的接入制式能力,rat-Type用于指示接入制式。ueCapabilityRAT-Container为该接入制式对应的能力字段。
S303,基站保存接收到UE发送的终端能力信息,并通过终端能力指示(UE Capability Indicator)消息将该UE的接入制式能力通知到核心网。后续该UE发起RRC连接后,核心网可以将该UE的接入制式能力发送给该UE接入的基站。
在源基站针对某个UE发起切换时,需要将该UE的接入制式能力转发给目的基站。如果切换涉及到核心网设备,那么UE的接入制式能力则通过源基站透传到核心网设备,然后再由核心网设备透传到目的基站。源基站将该UE的接入制式能力转发给目的基站的过程可以如图4所示。
S401,源基站在决定将UE切换到目的基站时,向目的基站发送切换请求(Handover  Request),Handover Request中携带该UE的接入制式能力。该UE的接入制式能力为源基站基于该UE上报的终端能力信息获取的,或者来源于核心网设备转发的该UE的接入制式能力。
S402,目的基站根据Handover Request消息中的UE的接入制式能力,以及UE当前的配置上下文,也就是源基站为该UE配置的无线资源信息等,来决定该UE在切换中使用的无线资源,然后通过切换请求确认(Handover Request ACK)消息发送给源基站。同时保存该UE的接入制式能力。
然而,UE上报的接入制式能力通过核心网或者源基站转发后,目的基站对于该UE的接入制式能力中各个接入制式的能力解读存在歧义。比如UE的接入制式能力中仅包含E-UTRAN能力,即仅包含E-UTRAN的接入制式标识和相应的能力字段,这时目的基站无法获知该UE是否支持其他接入制式,因为存在两种可能:
1)源基站查询该UE的接入制式能力时,只请求了E-UTRAN制式,所以UE只上报了E-UTRAN制式的接入能力。
2)源基站查询该UE的接入制式能力时,请求了多个接入制式,比如同时请求了E-UTRAN制式和NR制式。但是UE仅支持E-UTRAN制式,不支持NR制式,所以UE只上报了E-UTRAN制式的接入能力。
目的基站无法获知UE没有上报的接入制式的实际能力,这样如果目的基站需要这些接入制式能力时,只能再次发起能力查询流程,从而增加了空口开销和业务启动时延。
以下,对本申请中的部分用语进行解释说明,以便与本领域技术人员理解。
多个,是指两个或两个以上。
另外,需要理解的是,在本申请的描述中,“第一”、“第二”等词汇,仅用于区分描述的目的,而不能理解为指示或暗示相对重要性,也不能理解为指示或暗示顺序。
本申请实施例提供了一种无线通信方法及设备,用于解决基站可能无法准确获知UE的接入制式能力的问题。其中,方法和装置是基于同一发明构思的,由于方法及装置解决问题的原理相似,因此装置与方法的实施可以相互参见,重复之处不再赘述。
下面结合附图对本申请提供的无线通信方法进行具体说明。
参见图5,为本申请提供的无线通信方法的流程图。本申请提供的无线通信方法可以用于图1所示的通信系统。该方法具体可以如下。在本申请实施例中,终端能力请求中包括的元素名称,如列表、字段等元素的名称仅是一种示例性说明,并不对终端能力信息中各元素的命名进行限制。
在终端上报接入制式能力之前,终端可以先与第一网络设备建立RRC连接。其中,第一网络设备可以为基站。当终端与第一网路设备建立RRC连接之后,若第二网络设备向第一网络设备发送的初始上下文设置请求中没有携带该终端的接入制式能力,则执行步骤S501,其中,第二网络设备可以是核心网设备。为了描述方便,下面以第一网络设备为基站,第二网络设备为核心网设备为例对本申请实施例提供的无线通信方法进行说明。
S501,基站向终端发送终端能力请求消息。终端能力请求消息用于指示UE上报接入制式能力。其中,该终端能力请求消息中可以携带至少一个接入制式标识,以指示终端上报所述至少一个接入制式标识分别对应的接入能力。某接入制式标识对应的接入能力可以指终端接入该接入制式标识对应的接入制式的无线访问能力。
S502,终端根据基站发送的终端能力请求消息构造终端能力信息。该终端能力信息携 带终端不支持的接入制式标识。其中,终端能力信息中可以携带终端能力请求消息携带的至少一个接入制式标识中所有终端不支持的接入制式标识,也可以携带终端能力请求消息携带的至少一个接入制式标识中部分终端不支持的接入制式标识。
本申请实施例中通过终端在终端能力信息中增加终端不支持的接入制式标识,从而基站获取到终端的接入制式能力时,除了可以明确获知终端支持的接入制式,还可以获知终端不支持的接入制式,从而可以降低基站再次发起能力查询流程的几率,进而减少可以空口信令的开销,降低终端接入和业务启动的时延。
终端能力信息可以通过如下三种方式中的任一方式携带终端不支持的接入制式标识:
方式一,所述终端能力信息包括能力制式列表,所述能力制式列表包括至少一个支持的接入制式标识以及对应的能力字段、至少一个不支持的接入制式标识。
基于方式一,可以将接入制式标识对应的能力字段设为可选字段。针对终端能力请求消息携带的接入制式标识中的任一接入制式标识,若终端支持该接入制式标识对应的接入制式,则能力制式列表中包括该接入制式标识以及对应的能力字段。若终端不支持该接入制式标识对应的接入制式,则能力制式列表中包括该接入制式标识,且未包括该接入制式标识对应的能力字段。
因此,终端可以通过如下方式构造终端能力信息:在终端能力信息包括的接入制式列表中增加终端能力请求中携带的接入制式标识。对于终端能力请求消息中携带的任一接入制式标识,如果终端支持该接入制式,那么在终端能力信息中携带相应的待填充字段,并在对应的待填充字段中填充所述第一接入制式标识对应的能力字段。如果终端不支持该接入制式,那么不携带相应的能力字段。终端可以通过如下代码实现方式一:
Figure PCTCN2018081928-appb-000002
其中,UE-CapabilityRAT-ContainerList为能力制式列表,其中包括终端需要上报的接入制式能力。UE-CapabilityRAT-Container用于指示终端的接入制式能力,rat-Type用于指示接入制式。ueCapabilityRAT-Container为该接入制式对应的能力字段,这里ueCapabilityRAT-Container设置成可选的字段,若终端不支持该rat-Type指示的接入制式,则UE-CapabilityRAT-Container中没有该rat-Type对应的ueCapabilityRAT-Container字段,或者,UE-CapabilityRAT-Container中该rat-Type对应的ueCapabilityRAT-Container字段为空。
方式二,终端能力信息中携带请求列表以及能力制式列表,请求列表包括终端能力请求消息携带的接入制式标识,能力制式列表中包括终端支持的接入制式标识以及对应的能力字段。
基于方式二,可以在终端能力信息中增加请求列表,请求列表包括终端能力请求消息中携带的接入制式标识。针对终端能力请求消息携带的接入制式标识中的任一接入制式标识,若终端支持该接入制式标识对应的接入制式,则能力制式列表中包括该接入制式标识以及对应的能力字段。
因此,所述终端通过可以如下方式构造所述终端能力信息:终端在请求列表中填充终端能力请求消息中携带的至少一个接入制式标识。针对终端能力请求消息携带的接入制式标识中的任一接入制式标识,若终端支持该第二接入制式标识对应的接入制式,则终端在能力制式列表中设置该接入制式标识以及对应的待填充字段,并在对应的待填充字段中填充该接入制式标识对应的能力字段。终端可以通过如下代码实现方式二:
Figure PCTCN2018081928-appb-000003
其中,UE-CapabilityRAT-ContainerList为能力制式列表,其中包括终端支持的接入制式标识。UE-CapabilityRAT-Container用于指示支持的接入制式能力,rat-Type用于指示接入制式。ueCapabilityRAT-Container为该接入制式对应的能力字段。UE-CapabilityRATRequest为请求列表,其中包括终端能力请求中携带的接入制式标识。
方式三,所述终端能力信息携带能力制式列表以及不支持的能力制式列表,能力制式列表中包括终端支持的接入制式标识以及对应的能力字段。不支持的能力制式列表中包括终端不支持的接入制式标识。
基于方式三,可以在终端能力信息中增加不支持的能力制式列表。针对终端能力请求消息携带的接入制式标识中的任一接入制式标识,若终端支持该接入制式标识对应的接入制式,则能力制式列表中包括该接入制式标识以及对应的能力字段。若终端支持该接入制式标识对应的接入制式,则不支持的能力制式列表中包括该接入制式标识。
因此,所述终端可以通过如下方式构造终端能力信息:针对终端能力请求消息携带的接入制式标识中的任一接入制式标识,若终端支持该接入制式标识对应的接入制式,则终端在能力制式列表中设置该接入制式标识以及对应的待填充字段,并在对应的待填充字段中填充该接入制式标识对应的能力字段。若终端不支持该接入制式标识对应的接入制式,则终端在不支持的能力制式列表中设置该接入制式标识。终端可以通过如下代码实现方式三:
Figure PCTCN2018081928-appb-000004
其中,UE-CapabilityRAT-ContainerList为能力制式列表,其中包括终端支持的接入制式标识。UE-CapabilityRAT-Container为支持的接入制式能力,rat-Type用于指示接入制式, ueCapabilityRAT-Container为该接入制式对应的能力字段。UE-CapabilityRATRequest为不支持的能力制式列表,其中包括终端不支持的接入制式标识。
S503,终端将构造的终端能力信息发送给基站。
S504,基站在接收到终端的终端能力信息后,确定该终端的接入制式能力。
具体的,当终端采用方式一在终端能力信息中携带不支持的接入制式标识时,基站可以通过如下方式确定终端的接入制式能力:针对能力制式列表中的任一接入制式标识,若能力制式列表中包括该接入制式标识对应的能力字段,则基站确定终端支持该接入制式标识对应的接入制式。若能力制式列表中未包括该接入制式标识对应的能力字段,则基站确定终端不支持该接入制式标识的接入制式。
当终端采用方式二在终端能力信息中携带不支持的接入制式标识时,基站可以通过如下方式确定终端的接入制式能力:针对请求列表中的任一接入制式标识,若能力制式列表中包括该接入制式标识以及该接入制式标识对应的能力字段,则基站确定终端支持该接入制式标识对应的接入制式。若能力制式列表中未包括该接入制式标识以及该接入制式标识对应的能力字段,则基站确定终端不支持该接入制式标识对应的接入制式。
当终端采用方式三在终端能力信息中携带不支持的接入制式标识时,基站可以通过如下方式确定终端的接入制式能力:针对能力制式列表中的任一接入制式标识,基站确定终端支持该接入制式标识对应的接入制式。针对不支持的能力制式列表中的任一接入制式标识,基站确定终端不支持该接入制式标识对应的接入制式。
可选的,基站在接收到终端能力信息后,可以通过终端能力指示消息将该终端的终端能力信息通知到核心网设备。核心网设备在接收到该终端的终端能力信息后,可以将该终端的终端能力信息进行保存,并在该终端与基站建立RRC连接时,将该终端的终端能力信息通过初始上下文设置请求发送给与该终端建立RRC连接的基站。从而当与该终端建立RRC连接的基站接收到核心网设备发送的该终端的终端能力信息时,可以获知该终端的接入制式能力。
基站根据核心网设备转发的终端能力信息确定该终端的接入制式能力的过程,可以参阅步骤S504基站根据终端上报的终端能力信息确定该终端的接入制式能力的过程,本申请实施例在这里不再重复赘述。
基站(也就是终端接入的源基站)在需要将终端切换到其他基站(也就是终端需要切换到的目的基站)时,可以将该终端的接入制式能力转发给目的基站,从而目的基站在接收到源基站转发的该终端的接入制式能力时,可以获知该终端的接入制式能力。
目的基站根据源基站转发的终端能力信息确定该终端的接入制式能力的过程,可以参阅步骤S504基站根据终端上报的终端能力信息确定该终端的接入制式能力的过程,本申请实施例在这里不再重复赘述。
本发明实施例提供一种无线通信装置,具体用于实现图2至图5所述的实施例描述的方法,该装置可以是终端设备本身,也可以是终端设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分,该装置的结构如图6所示,包括通信接口601以及处理器602等物理器件,其中处理器602,可以是一个中央处理单元(central processing unit,CPU)、微处理器、专用集成电路、可编程逻辑电路、大规模集成电路、或者为数字处理单元等等。当装置是终端设备本身时,通信接口601用于终端设备和其他设备进行数据收发,通信接口601可以为射频收发器,主要用于将处理器602处理后的基带信号调制成高频无线信号 发送出去,并将接收到的高频无线信号处理成基带数据信号发送处理器602进行处理。当该装置是终端设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分时,通信接口601也可以为处理器与终端设备中的射频收发器之间的物理接口。该装置还可以包括存储器603,用于存储处理器602执行的程序,当然还可以存储终端设备需要的一些其他数据等。存储器603可以是易失性存储器(volatile memory),例如随机存取存储器(random-access memory,RAM)。存储器603也可以是非易失性存储器(non-volatile memory),例如只读存储器(read-only memory,ROM),快闪存储器(flash memory),硬盘(hard disk drive,HDD)或固态硬盘(solid-state drive,SSD)、或者存储器603是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器603可以是上述存储器的组合。
本申请实施例中不限定上述处理器602、存储器603以及通信接口601之间的具体连接介质。本申请实施例在图6中仅以存储器603、处理器602以及通信接口601之间通过总线604连接为例进行说明,总线在图6中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图6中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
处理器602可以是专用硬件或运行软件的处理器,当处理器602可以运行软件时,处理器602读取存储器603存储的指令,并在所述指令的驱动下,执行之前实施例中涉及的方法。
具体地,通信接口601,用于接收来自网络设备的终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力。所述网络设备可以为基站。处理器602,用于构造终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识。所述通信接口601,还用于向所述网络设备发送所述处理器602构造的所述终端能力信息。
在第一种具体实现方式中,所述终端能力信息包括能力制式列表,所述能力制式列表包括至少一个支持的接入制式标识以及对应的能力字段、至少一个不支持的接入制式标识,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
基于第一种具体实现方式,所述终端能力请求消息携带至少一个接入制式标识。若所述终端支持第一接入制式标识对应的第一接入制式,则所述能力制式列表中包括所述第一接入制式标识以及对应的能力字段。若所述终端不支持所述第一接入制式,则所述能力制式列表中包括所述第一接入制式标识,且未包括所述第一接入制式标识对应的能力字段。所述第一接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。
因此,所述处理器602,可以具体用于:在所述能力制式列表中设置所述第一接入制式标识以及对应的待填充字段。若所述无线通信装置支持所述第一接入制式,则在所述对应的待填充字段中填充所述第一接入制式标识对应的能力字段。
在第二种具体实现方式中,所述终端能力请求消息携带至少一个接入制式标识。所述终端能力信息中携带请求列表以及能力制式列表,所述请求列表包括所述终端能力请求消息携带的接入制式标识,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段。上述设计中,基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据请求列表中包括的、且能力制式列表中未包括的接入制式标识确定终 端不支持的接入制式,从而可以明确获知该终端的接入制式能力。
基于第二种具体实现方式,所述请求列表中包括第二接入制式标识。若所述终端支持第二接入制式标识对应的第二接入制式,则所述能力制式列表中包括所述第二接入制式标识以及对应的能力字段,所述第二接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。
因此,所述处理器602,可以具体用于:在所述请求列表中填充所述终端能力请求消息携带的接入制式标识。若所述无线通信装置支持所述第二接入制式,则在所述能力制式列表中设置所述第二接入制式标识以及对应的待填充字段,并在所述对应的待填充字段中填充所述第二接入制式标识对应的能力字段。
在第三种具体实现方式中,所述终端能力信息携带能力制式列表以及不支持的能力制式列表,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段。所述不支持的能力制式列表中包括至少一个不支持的接入制式标识。上述设计中,基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据不支持的能力制式列表包括的接入制式标识确定终端不支持的接入制式,从而可以明确获知该终端的接入制式能力。
基于第三种具体实现方式,若所述终端支持第三接入制式标识对应的第三接入制式,则所述能力制式列表中包括所述第三接入制式标识以及对应的能力字段,所述第三接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。若所述终端不支持所述第三接入制式,则所述不支持的能力制式列表中包括所述第三接入制式标识。
因此,所述处理器602,可以具体用于:若所述无线通信装置支持所述第三接入制式,则在所述能力制式列表中设置所述第三接入制式标识以及对应的待填充字段,并在所述对应的待填充字段中填充所述第三接入制式标识对应的能力字段。若所述无线通信装置不支持所述第三接入制式,则在所述不支持的能力制式列表中设置所述第三接入制式标识。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
当实施例提供的方法以软件或硬件或软硬件结合实现的时候,其对应的装置可以包括多个功能模块,每个功能模块可以包括软件、硬件或其结合。具体地,该装置如图7所示,其可以置于所述终端设备中。包括接收模块701,用于接收来自网络设备的终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力。构造模块702,用于构造终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识。发送模块703,用于向所述网络设备发送所述构造模块702构造的所述终端能力信息。
在第一种具体实现方式中,所述终端能力信息包括能力制式列表,所述能力制式列表包括至少一个支持的接入制式标识以及对应的能力字段、至少一个不支持的接入制式标识,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
基于第一种具体实现方式,所述终端能力请求消息携带至少一个接入制式标识。若所述终端支持第一接入制式标识对应的第一接入制式,则所述能力制式列表中包括所述第一 接入制式标识以及对应的能力字段。若所述终端不支持所述第一接入制式,则所述能力制式列表中包括所述第一接入制式标识,且未包括所述第一接入制式标识对应的能力字段。所述第一接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。
因此,所述构造模块702,可以具体用于:在所述能力制式列表中设置所述第一接入制式标识以及对应的待填充字段。若所述无线通信装置支持所述第一接入制式,则在所述对应的待填充字段中填充所述第一接入制式标识对应的能力字段。
在第二种具体实现方式中,所述终端能力请求消息携带至少一个接入制式标识。所述终端能力信息中携带请求列表以及能力制式列表,所述请求列表包括所述终端能力请求消息携带的接入制式标识,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段。上述设计中,基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据请求列表中包括的、且能力制式列表中未包括的接入制式标识确定终端不支持的接入制式,从而可以明确获知该终端的接入制式能力。
基于第二种具体实现方式,所述请求列表中包括第二接入制式标识。若所述终端支持第二接入制式标识对应的第二接入制式,则所述能力制式列表中包括所述第二接入制式标识以及对应的能力字段,所述第二接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。
因此,所述构造模块702,可以具体用于:在所述请求列表中填充所述终端能力请求消息携带的接入制式标识。若所述无线通信装置支持所述第二接入制式,则在所述能力制式列表中设置所述第二接入制式标识以及对应的待填充字段,并在所述对应的待填充字段中填充所述第二接入制式标识对应的能力字段。
在第三种具体实现方式中,所述终端能力信息携带能力制式列表以及不支持的能力制式列表,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段。所述不支持的能力制式列表中包括至少一个不支持的接入制式标识。上述设计中,基站可以根据能力制式列表中包括的接入制式标识确定终端支持的接入制式,根据不支持的能力制式列表包括的接入制式标识确定终端不支持的接入制式,从而可以明确获知该终端的接入制式能力。
基于第三种具体实现方式,若所述终端支持第三接入制式标识对应的第三接入制式,则所述能力制式列表中包括所述第三接入制式标识以及对应的能力字段,所述第三接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。若所述终端不支持所述第三接入制式,则所述不支持的能力制式列表中包括所述第三接入制式标识。
因此,所述构造模块702,可以具体用于:若所述无线通信装置支持所述第三接入制式,则在所述能力制式列表中设置所述第三接入制式标识以及对应的待填充字段,并在所述对应的待填充字段中填充所述第三接入制式标识对应的能力字段。若所述无线通信装置不支持所述第三接入制式,则在所述不支持的能力制式列表中设置所述第三接入制式标识。
本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,另外,在本申请各个实施例中的各功能模块可以集成在一个处理器中,也可以是单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。其中,集成的模 块既可以采用硬件的形式实现时,构造模块702可以是处理器602。接收模块701和发送模块703可以是通信接口601。
本发明实施例提供一种无线通信装置,具体用于实现图2至图5所述的实施例描述的方法,该装置可以为与终端建立RRC连接的源基站,也可以为终端进行小区切换时接入的目的基站。该装置可以是基站本身,也可以是基站中的芯片或芯片组或芯片中用于执行相关方法功能的一部分,该装置的结构如图8所示,包括通信接口801以及处理器802等物理器件,其中处理器802,可以是CPU、微处理器、专用集成电路、可编程逻辑电路、大规模集成电路、或者为数字处理单元等等。当装置是基站本身时,通信接口801用于终端设备和其他设备进行数据收发,通信接口801可以为射频收发器,主要用于将处理器802处理后的基带信号调制成高频无线信号发送出去,并将接收到的高频无线信号处理成基带数据信号发送处理器802进行处理。当该装置是基站中的芯片或芯片组或芯片中用于执行相关方法功能的一部分时,通信接口801也可以为处理器与终端设备中的射频收发器之间的物理接口。该装置还可以包括存储器803,用于存储处理器802执行的程序,当然还可以存储终端设备需要的一些其他数据等。存储器803可以是volatile memory,例如RAM。存储器803也可以是non-volatile memory,例如ROM,flash memory,HDD或SSD、或者存储器803是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器803可以是上述存储器的组合。
本申请实施例中不限定上述处理器802、存储器803以及通信接口801之间的具体连接介质。本申请实施例在图8中仅以存储器803、处理器802以及通信接口801之间通过总线804连接为例进行说明,总线在图8中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图8中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
处理器802可以是专用硬件或运行软件的处理器,当处理器802可以运行软件时,处理器802读取存储器803存储的指令,并在所述指令的驱动下,执行之前实施例中涉及的方法。
具体地,通信接口801,用于接收终端能力信息,所述终端能力信息中携带终端不支持的接入制式标识,所述终端能力信息来自所述终端,或者所述终端能力信息来自第二网络设备,所述n为大于0的整数,第二网络设备可以为其它基站,也可以为核心网设备。处理器802,用于根据所述通信接口801接收的所述终端能力信息确定所述终端的接入制式能力。终端能力信息可以为图2至图5所述的终端能力信息。
可选的,所述终端能力信息来自所述终端,所述通信接口801,还用于:在接收终端的终端能力信息之前,向所述终端发送终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力。
所述通信接口801,还可以用于:在接收终端的终端能力信息之后,向第三网络设备发送所述终端能力信息。第三网络设备可以为其它基站,也可以为核心网设备。
在一种具体实现方式中,所述处理器802,可以具体用于:若所述能力制式列表中包括第二接入制式标识对应的能力字段,确定所述终端支持所述第二接入制式标识对应的第二接入制式,所述第二接入制式标识为所述能力制式列表中包括的任一接入制式标识。或者,若所述能力制式列表中未包括所述第二接入制式标识对应的能力字段,确定所述终端不支持所述第二接入制式。
在另一种具体实现方式中,所述处理器802,可以具体用于:若所述能力制式列表中包括第四接入制式标识以及所述第四接入制式标识对应的能力字段,确定所述终端支持所述第四接入制式标识对应的第四接入制式,所述第四接入制式标识为所述请求列表中包括的任一接入制式标识。或者,若所述能力制式列表中未包括所述第四接入制式标识以及所述第四接入制式标识对应的能力字段,确定所述终端不支持所述第四接入制式。
在另一种具体实现方式中,所述处理器802,可以具体用于:确定所述终端支持第六接入制式标识对应的接入制式,所述第六接入制式标识为所述能力制式列表中的任一接入制式标识。或者,确定所述终端不支持第七接入制式标识对应的接入制式,所述第七接入制式标识为所述不支持的能力制式列表中的任一接入制式标识。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
当实施例提供的方法以软件或硬件或软硬件结合实现的时候,其对应的装置可以包括多个功能模块,每个功能模块可以包括软件、硬件或其结合。具体地,该装置如图9所示,其可以置于所述基站中。包括接收模块901,用于接收终端能力信息,所述终端能力信息中携带终端不支持的接入制式标识,所述终端能力信息来自所述终端,或者所述终端能力信息来自第二网络设备,其中第二网络设备可以为其他基站,或者核心网设备,所述n为大于0的整数。确定模块902,用于根据所述接收模块901接收的所述终端能力信息确定所述终端的接入制式能力。
若所述终端能力信息来自所述终端,所述基站还可以包括发送模块903,用于:在所述接收模块901接收终端的终端能力信息之前,向所述终端发送终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力。
可选的,所述发送模块903,还可以用于:在所述接收模块901接收终端的终端能力信息之后,向第三网络设备发送所述终端能力信息,所述第三网络设备可以为其他基站,也可以为核心网设备。
在一种具体实现方式中,所述确定模块902,可以具体用于:若所述能力制式列表中包括第二接入制式标识对应的能力字段,确定所述终端支持所述第二接入制式标识对应的第二接入制式,所述第二接入制式标识为所述能力制式列表中包括的任一接入制式标识。或者,若所述能力制式列表中未包括所述第二接入制式标识对应的能力字段,确定所述终端不支持所述第二接入制式。
在另一种具体实现方式中,所述确定模块902,可以具体用于:若所述能力制式列表中包括第四接入制式标识以及所述第四接入制式标识对应的能力字段,确定所述终端支持所述第四接入制式标识对应的第四接入制式,所述第四接入制式标识为所述请求列表中包括的任一接入制式标识。或者,若所述能力制式列表中未包括所述第四接入制式标识以及所述第四接入制式标识对应的能力字段,确定所述终端不支持所述第四接入制式。
在另一种具体实现方式中,所述确定模块902,可以具体用于:确定所述终端支持第六接入制式标识对应的接入制式,所述第六接入制式标识为所述能力制式列表中的任一接入制式标识。或者,确定所述终端不支持第七接入制式标识对应的接入制式,所述第七接 入制式标识为所述不支持的能力制式列表中的任一接入制式标识。
本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,另外,在本申请各个实施例中的各功能模块可以集成在一个处理器中,也可以是单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。其中,集成的模块既可以采用硬件的形式实现时,确定模块902可以是处理器802。接收模块901和发送模块903可以是通信接口801。
本发明实施例提供一种无线通信装置,具体用于实现图2至图5所述的实施例描述的方法,该装置可以是核心网设备本身,也可以是核心网设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分,该装置的结构如图10所示,包括通信接口1001以及处理器1002等物理器件,其中处理器1002,可以是CPU、微处理器、专用集成电路、可编程逻辑电路、大规模集成电路、或者为数字处理单元等等。当装置是核心网设备本身时,通信接口1001用于终端设备和其他设备进行数据收发,通信接口1001可以为射频通信接口件,主要用于将处理器1002处理后的基带信号调制成高频无线信号发送出去,并将接收到的高频无线信号处理成基带数据信号发送处理器1002进行处理。当该装置是核心网设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分时,通信接口601也可以为处理器与终端设备中的射频收发器之间的物理接口。该装置还可以包括存储器1003,用于存储处理器1002执行的程序,当然还可以存储终端设备需要的一些其他数据等。存储器1003可以是volatile memory,例如RAM。存储器1003也可以是non-volatile memory,例如ROM,flash memory,HDD或SSD、或者存储器1003是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器1003可以是上述存储器的组合。
本申请实施例中不限定上述处理器1002、存储器1003以及通信接口1001之间的具体连接介质。本申请实施例在图10中仅以存储器1003、处理器1002以及通信接口1001之间通过总线1004连接为例进行说明,总线在图10中以粗线表示,其它部件之间的连接方式,仅是进行示意性说明,并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示,图10中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
处理器1002可以是专用硬件或运行软件的处理器,当处理器1002可以运行软件时,处理器1002读取存储器1003存储的指令,并在所述指令的驱动下,执行之前实施例中涉及的方法。
具体地,通信接口1001,用于接收来自第二网络设备的终端能力信息,所述终端能力信息中携带终端能力请求消息携带的接入制式标识中所述终端不支持的接入制式标识,以及所述终端能力请求消息携带的接入制式标识中所述终端支持的接入制式标识。第二网络设备可以为基站。处理器1002,用于将所述通信接口1001接收的所述终端能力信息保存在存储器1003,并通过所述通信接口1001向第二网络设备发送所述终端能力信息。终端能力信息可以为图2至图5所述的终端能力信息。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
当实施例提供的方法以软件或硬件或软硬件结合实现的时候,其对应的装置可以包括多个功能模块,每个功能模块可以包括软件、硬件或其结合。具体地,该装置如图11所示,其可以置于所述核心网设备中。包括接收模块1101,用于接收来自其他网络设备的终端能力信息,所述其他网络设备可以为基站,所述终端能力信息中携带终端能力请求消息携带的接入制式标识中所述终端不支持的接入制式标识,以及所述终端能力请求消息携带的接入制式标识中所述终端支持的接入制式标识。保存模块1102,用于将所述接收模块1101接收的所述终端能力信息进行保存。发送模块1103,用于向第二网络设备发送所述保存模块1102保存的终端能力信息。
本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,另外,在本申请各个实施例中的各功能模块可以集成在一个处理器中,也可以是单独物理存在,也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。其中,集成的模块既可以采用硬件的形式实现时,保存模块1102可以是处理器1002。接收模块1101和发送模块1103可以是通信接口1001。
本发明实施例还提供了一种计算机可读存储介质,用于存储为执行上述处理器所需执行的计算机软件指令,其包含用于执行上述处理器所需执行的程序。
本申请实施例提供一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行图2至图5所述的无线通信方法。
本领域内的技术人员应明白,本申请的实施例可提供为方法、系统、或计算机程序产品。因此,本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样,倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。

Claims (34)

  1. 一种无线通信方法,其特征在于,包括:
    终端接收网络设备发送的终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力;
    所述终端向所述网络设备发送终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识。
  2. 如权利要求1所述的方法,其特征在于,所述终端能力信息包括能力制式列表,所述能力制式列表包括至少一个支持的接入制式标识以及对应的能力字段、至少一个不支持的接入制式标识,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  3. 如权利要求2所述的方法,其特征在于,所述终端能力请求消息携带至少一个接入制式标识;
    若所述终端支持第一接入制式标识对应的第一接入制式,则所述能力制式列表中包括所述第一接入制式标识以及对应的能力字段;
    若所述终端不支持所述第一接入制式,则所述能力制式列表中包括所述第一接入制式标识,且未包括所述第一接入制式标识对应的能力字段;
    其中,所述第一接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。
  4. 如权利要求1所述的方法,其特征在于,所述终端能力请求消息携带至少一个接入制式标识;
    所述终端能力信息中携带请求列表以及能力制式列表,所述请求列表包括所述终端能力请求消息携带的接入制式标识,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  5. 如权利要求4所述的方法,其特征在于,所述请求列表中包括第二接入制式标识;
    若所述终端支持所述第二接入制式标识对应的第二接入制式,则所述能力制式列表中包括所述第二接入制式标识以及对应的能力字段,所述第二接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。
  6. 如权利要求1所述的方法,其特征在于,所述终端能力信息携带能力制式列表以及不支持的能力制式列表,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段;所述不支持的能力制式列表中包括至少一个不支持的接入制式标识;
    其中,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  7. 如权利要求6所述的方法,其特征在于,若所述终端支持第三接入制式标识对应的第三接入制式,则所述能力制式列表中包括所述第三接入制式标识以及对应的能力字段;
    若所述终端不支持所述第三接入制式,则所述不支持的能力制式列表中包括所述第三接入制式标识;
    所述第三接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入 制式标识。
  8. 一种无线通信方法,其特征在于,包括:
    第一网络设备向终端发送终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力;
    所述第一网络设备接收终端上报的终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识。
  9. 如权利要求8所述的方法,其特征在于,还包括:
    所述第一网络设备根据所述终端能力信息确定所述终端针对所述终端能力请求消息携带的接入制式标识分别对应的接入能力;或者
    所述第一网络设备在与所述终端建立无线资源控制RRC连接时,将所述终端能力信息转发给第二网络设备,以使所述第二网络设备保存所述终端的接入制式能力;或者
    所述第一网络设备在将所述终端切换到第三网络设备时,将所述终端能力信息转发给所述第三网络设备,以使所述第三网络设备确定所述终端针对所述终端能力请求消息携带的接入制式标识分别对应的接入能力。
  10. 一种无线通信方法,其特征在于,包括:
    第一网络设备接收并保存第二网络设备发送的终端能力信息,所述终端能力信息中携带终端不支持的接入制式标识;
    所述第一网络设备向第三网络设备发送所述终端能力信息。
  11. 一种无线通信方法,其特征在于,包括:
    第一网络设备接收第二网络设备发送的终端能力信息,所述终端能力信息中携带终端不支持的接入制式标识;
    所述第一网络设备根据所述终端能力信息确定所述终端的接入制式能力。
  12. 如权利要求11所述的方法,其特征在于,所述终端能力信息包括能力制式列表,所述能力制式列表包括至少一个支持的接入制式标识以及对应的能力字段、至少一个不支持的接入制式标识,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  13. 如权利要求12所述的方法,其特征在于,所述第一网络设备根据所述终端能力信息确定所述终端的接入制式能力,包括:
    若所述能力制式列表中包括第二接入制式标识对应的能力字段,所述第一网络设备确定所述终端支持所述第二接入制式标识对应的第二接入制式,所述第二接入制式标识为所述能力制式列表中包括的任一接入制式标识;或者
    若所述能力制式列表中未包括所述第二接入制式标识对应的能力字段,所述第一网络设备确定所述终端不支持所述第二接入制式。
  14. 如权利要求11所述的方法,其特征在于,所述终端能力请求消息携带至少一个接入制式标识;
    所述终端能力信息中携带请求列表以及能力制式列表,所述请求列表包括所述终端能力请求消息携带的接入制式标识,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  15. 如权利要求14所述的方法,其特征在于,所述第一网络设备根据所述终端能力 信息确定所述终端的接入制式能力,包括:
    若所述能力制式列表中包括第四接入制式标识以及所述第四接入制式标识对应的能力字段,所述第一网络设备确定所述终端支持所述第四接入制式标识对应的第四接入制式,所述第四接入制式标识为所述请求列表中包括的任一接入制式标识;或者
    若所述能力制式列表中未包括所述第四接入制式标识以及所述第四接入制式标识对应的能力字段,所述第一网络设备确定所述终端不支持所述第四接入制式。
  16. 如权利要求11所述的方法,其特征在于,所述终端能力信息携带能力制式列表以及不支持的能力制式列表,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段;所述不支持的能力制式列表中包括至少一个不支持的接入制式标识;
    其中,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  17. 如权利要求16所述的方法,其特征在于,所述第一网络设备根据所述终端能力信息确定所述终端的接入制式能力,包括:
    所述第一网络设备确定所述终端支持第六接入制式标识对应的接入制式,所述第六接入制式标识为所述能力制式列表中的任一接入制式标识;或者
    所述第一网络设备确定所述终端不支持第七接入制式标识对应的接入制式,所述第七接入制式标识为所述不支持的能力制式列表中的任一接入制式标识。
  18. 一种无线通信装置,其特征在于,包括:
    通信接口,用于接收来自网络设备的终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力;
    处理器,用于构造终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识;
    所述通信接口,还用于向所述网络设备发送所述处理器构造的所述终端能力信息。
  19. 如权利要求18所述的装置,其特征在于,所述终端能力信息包括能力制式列表,所述能力制式列表包括至少一个支持的接入制式标识以及对应的能力字段、至少一个不支持的接入制式标识,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  20. 如权利要求19所述的装置,其特征在于,所述终端能力请求消息携带至少一个接入制式标识;
    若所述终端支持第一接入制式标识对应的第一接入制式,则所述能力制式列表中包括所述第一接入制式标识以及对应的能力字段;
    若所述终端不支持所述第一接入制式,则所述能力制式列表中包括所述第一接入制式标识,且未包括所述第一接入制式标识对应的能力字段;
    其中,所述第一接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。
  21. 如权利要求18所述的装置,其特征在于,所述终端能力请求消息携带至少一个接入制式标识;
    所述终端能力信息中携带请求列表以及能力制式列表,所述请求列表包括所述终端能力请求消息携带的接入制式标识,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述 任意一个接入制式标识所对应接入制式的接入能力。
  22. 如权利要求21所述的装置,其特征在于,所述请求列表中包括第二接入制式标识;
    若所述终端支持所述第二接入制式标识对应的第二接入制式,则所述能力制式列表中包括所述第二接入制式标识以及对应的能力字段,所述第二接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。
  23. 如权利要求18所述的装置,其特征在于,所述终端能力信息携带能力制式列表以及不支持的能力制式列表,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段;所述不支持的能力制式列表中包括至少一个不支持的接入制式标识;
    其中,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  24. 如权利要求23所述的装置,其特征在于,若所述终端支持第三接入制式标识对应的第三接入制式,则所述能力制式列表中包括所述第三接入制式标识以及对应的能力字段;
    若所述终端不支持所述第三接入制式,则所述不支持的能力制式列表中包括所述第三接入制式标识;
    所述第三接入制式标识为所述终端能力请求消息携带的接入制式标识中的任一接入制式标识。
  25. 一种无线通信装置,其特征在于,包括处理器和通信接口;
    所述处理器,用于通过所述通信接口向终端发送终端能力请求消息,终端能力请求消息用于指示UE上报接入制式能力;
    所述通信接口,还用于接收终端上报的终端能力信息,所述终端能力信息中携带所述终端不支持的接入制式标识。
  26. 如权利要求25所述的装置,其特征在于,所述处理器,还用于根据所述终端能力信息确定所述终端的接入制式能力;或者
    所述处理器,还用于在与所述终端建立无线资源控制RRC连接时,通过所述通信接口将所述终端能力信息转发给第二网络设备,以使所述第二网络设备保存所述终端的接入制式能力;或者
    所述处理器,还用于在将所述终端切换到第三网络设备时,通过所述通信接口将所述终端能力信息转发给第三网络设备,以使所述第三网络设备确定所述终端的接入制式能力。
  27. 一种无线通信装置,其特征在于,包括处理器和通信接口;
    所述处理器,用于通过所述通信接口接收来自第二网络设备的终端能力信息,所述终端能力信息中携带终端不支持的接入制式标识;并将所述终端能力信息进行保存;
    所述通信接口,还用于向第三网络设备发送所述终端能力信息。
  28. 一种无线通信装置,其特征在于,包括处理器和通信接口;
    所述通信接口,用于接收来自第二网络设备的终端能力信息,所述终端能力信息中携带终端不支持的接入制式标识;
    所述处理器,用于根据所述终端能力信息确定所述终端的接入制式能力。
  29. 如权利要求28所述的装置,其特征在于,所述终端能力信息包括能力制式列表, 所述能力制式列表包括至少一个支持的接入制式标识以及对应的能力字段、至少一个不支持的接入制式标识,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  30. 如权利要求29所述的装置,其特征在于,所述处理器,具体用于:
    若所述能力制式列表中包括第二接入制式标识对应的能力字段,确定所述终端支持所述第二接入制式标识对应的第二接入制式,所述第二接入制式标识为所述能力制式列表中包括的任一接入制式标识;或者
    若所述能力制式列表中未包括所述第二接入制式标识对应的能力字段,确定所述终端不支持所述第二接入制式。
  31. 如权利要求28所述的装置,其特征在于,所述终端能力请求消息携带至少一个接入制式标识;
    所述终端能力信息中携带请求列表以及能力制式列表,所述请求列表包括所述终端能力请求消息携带的接入制式标识,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  32. 如权利要求31所述的装置,其特征在于,所述处理器,具体用于:
    若所述能力制式列表中包括第四接入制式标识以及所述第四接入制式标识对应的能力字段,确定所述终端支持所述第四接入制式标识对应的第四接入制式,所述第四接入制式标识为所述请求列表中包括的任一接入制式标识;或者
    若所述能力制式列表中未包括所述第四接入制式标识以及所述第四接入制式标识对应的能力字段,确定所述终端不支持所述第四接入制式。
  33. 如权利要求28所述的装置,其特征在于,所述终端能力信息携带能力制式列表以及不支持的能力制式列表,所述能力制式列表中包括至少一个支持的接入制式标识以及对应的能力字段;所述不支持的能力制式列表中包括至少一个不支持的接入制式标识;
    其中,任意一个接入制式标识对应的能力字段用于表征所述终端接入所述任意一个接入制式标识所对应接入制式的接入能力。
  34. 如权利要求33所述的装置,其特征在于,所述处理器,具体用于:
    确定所述终端支持第六接入制式标识对应的接入制式,所述第六接入制式标识为所述能力制式列表中的任一接入制式标识;或者
    确定所述终端不支持第七接入制式标识对应的接入制式,所述第七接入制式标识为所述不支持的能力制式列表中的任一接入制式标识。
PCT/CN2018/081928 2018-04-04 2018-04-04 一种无线通信方法及设备 WO2019191943A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/081928 WO2019191943A1 (zh) 2018-04-04 2018-04-04 一种无线通信方法及设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/081928 WO2019191943A1 (zh) 2018-04-04 2018-04-04 一种无线通信方法及设备

Publications (1)

Publication Number Publication Date
WO2019191943A1 true WO2019191943A1 (zh) 2019-10-10

Family

ID=68099894

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081928 WO2019191943A1 (zh) 2018-04-04 2018-04-04 一种无线通信方法及设备

Country Status (1)

Country Link
WO (1) WO2019191943A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210250753A1 (en) * 2020-02-10 2021-08-12 Qualcomm Incorporated Signaling of capability information by user equipment

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101193419A (zh) * 2006-11-28 2008-06-04 中兴通讯股份有限公司 一种移动终端使用非连续接收特性的方法
US20100061307A1 (en) * 2008-09-11 2010-03-11 Samsung Electronics Co., Ltd. Method and apparatus for supporting multiple MAC versions in broadband wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101193419A (zh) * 2006-11-28 2008-06-04 中兴通讯股份有限公司 一种移动终端使用非连续接收特性的方法
US20100061307A1 (en) * 2008-09-11 2010-03-11 Samsung Electronics Co., Ltd. Method and apparatus for supporting multiple MAC versions in broadband wireless communication system

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210250753A1 (en) * 2020-02-10 2021-08-12 Qualcomm Incorporated Signaling of capability information by user equipment
US11706610B2 (en) * 2020-02-10 2023-07-18 Qualcomm Incorporated Signaling of capability information by user equipment
US12069767B2 (en) 2020-02-10 2024-08-20 Qualcomm Incorporated Signaling of capability information by user equipment

Similar Documents

Publication Publication Date Title
KR102635070B1 (ko) 통신 방법 및 통신 장치
US11323920B2 (en) Handover method, base station, and communications system
RU2643505C2 (ru) Способ для получения возможностей ue, оконечное устройство и базовая станция
WO2018202138A1 (zh) 通信方法及相关设备
CN110913472B (zh) 定位管理方法、装置、5g无线接入网节点及核心网节点
EP3531723B1 (en) Indication method and related device
WO2019052168A1 (zh) 配置anr的方法、终端设备、基站和核心网设备
WO2019062152A1 (zh) 通信方法和设备
KR102491526B1 (ko) 이중 연결을 위한 자동 이웃 관계 개선 기법
WO2019153265A1 (zh) 无线通信的方法和网络设备
WO2018145625A1 (zh) 一种寻呼方法和基站
JP2021522761A (ja) ハンドオーバプロセスにおけるサービス処理方法および装置、端末およびネットワーク機器
EP3813301A1 (en) Data transmission method, terminal device and network device
WO2018137716A1 (zh) 一种保持udc功能连续性的方法及设备
WO2018137579A1 (zh) 通信方法和设备
EP3920585A1 (en) Communication system handover method, network device, apparatus and medium
WO2019047117A1 (zh) 接入网络的方法、终端设备和网络设备
JP2018516031A (ja) 情報通知方法、ユーザ端末、第1の基地局および第2の基地局
WO2020192387A1 (zh) 一种请求处理方法、相关装置及系统
JP2019534636A (ja) セッション管理方法及びセッション管理ネットワーク要素
US11622403B2 (en) Data sending method, apparatus, and system
CN110474742B (zh) 一种确定rrm测量配置的方法及设备
WO2019191943A1 (zh) 一种无线通信方法及设备
JP2019530992A (ja) 通信方法及び通信装置
CN114501612B (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: 18913936

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: 18913936

Country of ref document: EP

Kind code of ref document: A1