WO2018036421A1 - 网络接入方法、接入设备和终端设备 - Google Patents

网络接入方法、接入设备和终端设备 Download PDF

Info

Publication number
WO2018036421A1
WO2018036421A1 PCT/CN2017/098038 CN2017098038W WO2018036421A1 WO 2018036421 A1 WO2018036421 A1 WO 2018036421A1 CN 2017098038 W CN2017098038 W CN 2017098038W WO 2018036421 A1 WO2018036421 A1 WO 2018036421A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
message
type
access
rrc connection
Prior art date
Application number
PCT/CN2017/098038
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 EP17842844.7A priority Critical patent/EP3477999B1/en
Publication of WO2018036421A1 publication Critical patent/WO2018036421A1/zh
Priority to US16/281,815 priority patent/US10834775B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/18Selecting a network or a communication service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/15Setup of multiple wireless link connections
    • H04W76/16Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00Modulated-carrier systems
    • H04L27/26Systems using multi-frequency codes
    • H04L27/2601Multicarrier modulation systems
    • H04L27/2602Signal structure
    • H04L27/2605Symbol extensions, e.g. Zero Tail, Unique Word [UW]
    • H04L27/2607Cyclic extensions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0091Signaling for the administration of the divided path
    • H04L5/0094Indication of how sub-channels of the path are allocated
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446Resources in time domain, e.g. slots or frames
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453Resources in frequency domain, e.g. a carrier in FDMA
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/27Transitions between radio resource control [RRC] states
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/0001Arrangements for dividing the transmission path
    • H04L5/0003Two-dimensional division
    • H04L5/0005Time-frequency

Definitions

  • the present application relates to communications technologies, and in particular, to a network access method, an access device, and a terminal device.
  • NR New Radio Access Technology
  • LTE Long Term Evolution
  • the NR site and the NR core network are included; wherein the NR site provides different air interfaces than the evolved base station (Evolved NodeB, eNB for short) in the LTE system, for example, a shorter transmission time interval. (Transmission Time Interval, TTI for short), larger bandwidth, etc.
  • the NR core network of the NR system can support more service types than the Evolved Packet Core (EPC) in the LTE system. .
  • EPC Evolved Packet Core
  • the terminal device of the LTE accesses the EPC through the eNB, and the terminal device of the NR accesses the NR core network through the NR site.
  • the LTE system smoothly evolves to the NR system, that is, a scenario in which both the LTE system and the NR system exist simultaneously.
  • the access device cannot determine which system the core network to connect the terminal device to.
  • the present application provides a network access method, an access device, and a terminal device to solve the problem in the prior art that in the scenario where the LTE system and the NR system exist simultaneously, the access device cannot determine which system the core device is connected to. The problem.
  • the application provides a network access method, including:
  • the access device is connected to at least two different types of core networks, and the different types of terminal devices have the capability of connecting to different types of core networks.
  • the access devices are sent to indicate the types of the terminal devices.
  • the first message is that the access device determines the type of the terminal device according to the first message, and further determines the type of the terminal device according to the first message, and determines the target core network to which the terminal device is connected according to the type of the terminal device, thereby enabling simultaneous implementation of the target core network
  • the access device accurately connects the terminal device to the target core network.
  • the first message is a preamble sequence
  • the access device includes:
  • the access device determines that the type of the terminal device is the first type according to the correspondence between the preamble sequence and the first type of terminal device.
  • the first message is a preamble sequence
  • the preamble sequence includes first indication information, where the first indication information is used to indicate that the type of the terminal device is a first type.
  • the access device determines, according to the correspondence between the preamble sequence and the first type of terminal device, that the type of the terminal device is the first type, including:
  • the access device determines that the type of the terminal device is the first type according to the time-frequency resource of the preamble sequence and the correspondence between the time-frequency resource and the terminal device of the first type.
  • the access device determines, according to the first message, that the type of the terminal device is the first type, including:
  • the access device determines, according to the frame length, the subcarrier interval, the cyclic prefix CP length, or the transmission time interval TTI length used for transmitting the first message, that the type of the terminal device is the first type.
  • the first message is a radio resource control RRC connection request message, where the RRC connection request message includes second indication information, where the second indication information is used to indicate the type of the terminal device.
  • the first message is an RRC connection setup complete message
  • the RRC connection setup complete message includes third indication information, where the third indication information is used to indicate that the type of the terminal device is The first type.
  • the first message is an RRC connection setup complete message
  • the RRC connection setup complete message includes a non-access stratum NAS message
  • the NAS message includes fourth indication information, where the The four indication information is used to indicate that the type of the terminal device is the first type.
  • the first message is an RRC connection request message or an RRC connection setup complete message
  • the access device includes:
  • the access device determines, according to the format of the RRC connection request message or the RRC connection setup complete message, that the type of the terminal device is the first type.
  • the first message is an RRC connection setup complete message
  • the access device includes:
  • the access device determines, according to the format of the NAS message in the RRC connection setup complete message, that the type of the terminal device is the first type.
  • the method before the access device receives the first message sent by the terminal device, the method further includes:
  • the access device sends the capability indication information to the terminal device, where the capability indication information is used to indicate that the access device has the capability of accessing the first core network.
  • the application provides a network access method, including:
  • the terminal device generates a first message
  • the terminal device sends the first message to the access device, where the first message is used to indicate that the terminal device is the first type of terminal device, where the first type of terminal device has access to the first core network. Capability, the access device is connected to at least two different types of core networks, the at least two different core networks including the The first core network.
  • the method before the terminal device generates the first message, the method further includes:
  • the terminal device determines a format of the first message according to the target core network to be accessed.
  • the method before the terminal device sends the first message to the access device, the method further includes:
  • the terminal device determines that the access device has the capability of accessing the first core network.
  • the method before the terminal device determines that the access device has the capability of accessing the first core network, the method further includes:
  • the terminal device Receiving, by the terminal device, a broadcast message, where the broadcast message includes capability indication information, where the capability indication information is used to indicate that the access device has the capability of accessing the first core network;
  • the terminal device receives the random access response information, where the random access response information includes the capability indication information;
  • the terminal device receives a radio resource control RRC connection setup message, where the RRC connection setup message includes the capability indication information.
  • the first message is a preamble sequence
  • the terminal device generates a first message, including:
  • the terminal device determines the preamble sequence according to the correspondence between the preamble sequence and the first type of terminal device.
  • the first message is a preamble sequence
  • the preamble sequence includes first indication information, where the first indication information is used to indicate that the type of the terminal device is a first type.
  • the terminal device determines the preamble sequence according to the correspondence between the preamble sequence and the first type of terminal device, including:
  • the terminal device determines to send the time-frequency resource of the preamble sequence to the access device according to the correspondence between the time-frequency resource and the first type of terminal device.
  • the terminal device sends the first message to the access device, including:
  • the terminal device transmits the first message according to a frame length, a subcarrier interval, a cyclic prefix CP length, or a transmission time interval TTI length used by the first message of the first type of terminal device.
  • the first message is a radio resource control RRC connection request message, where the RRC connection request message includes second indication information, where the second indication information is used to indicate the type of the terminal device. For the first type.
  • the first message is an RRC connection setup complete message
  • the RRC connection setup complete message includes third indication information, where the third indication information is used to indicate that the type of the terminal device is The first type.
  • the first message is an RRC connection setup complete message
  • the RRC connection setup complete message includes a non-access stratum NAS message
  • the NAS message includes fourth indication information, where the The four indication information is used to indicate that the type of the terminal device is the first type.
  • the first message is an RRC connection request message or an RRC connection setup complete message
  • the terminal device generates a first message, including:
  • the terminal device generates a first message according to a format of an RRC connection request message or an RRC connection setup complete message of the target core network to be accessed.
  • the first message is an RRC connection setup complete message
  • the terminal device generates a first message, including:
  • the terminal device generates a first message according to the format of the NAS message in the RRC connection setup complete message of the target core network to be accessed.
  • the application provides an access device, where the access device has the function of implementing the behavior of the access device in the foregoing access method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the access device includes multiple function modules, where the network access method of any one of the foregoing first aspects is implemented, so that the access device determines the target of the terminal device connection.
  • the core network and thus, in the scenario where both the LTE system and the NR system exist, the access device accurately connects the terminal device to the target core network.
  • the structure of the access device includes a processor and a transceiver, and the processor is configured to support the access device to perform a corresponding function in the foregoing network access method.
  • the receiver or the transmitter is configured to support communication between the access device and the terminal device and the core network, and send information or instructions involved in the network access method to the terminal device or the core network.
  • the access device can also include a memory for coupling with the processor that retains the program instructions and data necessary to access the device.
  • the application provides a terminal device, where the terminal device has a function of implementing the behavior of the terminal device in the foregoing access method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the terminal device includes a plurality of functional modules, configured to implement any one of the network access methods in the foregoing second aspect, by sending a message to the access device, indicating the terminal.
  • the type of the device enables the access device to determine the target core network to which the terminal device is connected according to the type of the terminal device. Therefore, in the scenario where the LTE system and the NR system exist simultaneously, the access device can accurately connect the terminal device to the target. Core Network.
  • the structure of the terminal device includes a processor and a transceiver, and the processor is configured to support the terminal device to perform a corresponding function in the foregoing network access method.
  • the receiver or the transmitter is configured to support communication between the terminal device and the access device, and send information or instructions involved in the network access method to the access device.
  • a memory may also be included in the terminal device for coupling with the processor, which stores program instructions and data necessary to access the device.
  • FIG. 1 is a schematic diagram of a network access system provided by the present application.
  • Embodiment 1 of a network access method according to the present application
  • Embodiment 3 is a schematic flowchart of Embodiment 2 of a network access method according to the present application.
  • Embodiment 5 of a network access method according to the present application.
  • Embodiment 6 of a network access method according to the present application.
  • FIG. 6 is a schematic structural diagram of an embodiment of an access device according to the present application.
  • FIG. 7 is a schematic structural diagram of an embodiment of a terminal device according to the present application.
  • the wireless communication system is also continually evolving.
  • the present application provides an access device, which can simultaneously connect at least Two different types of core networks, and can be connected to the terminal devices corresponding to the at least two different core networks at the same time, wherein the terminal devices corresponding to the core network of the pre-evolution system can only be connected to the core network of the pre-evolved system.
  • the device on the terminal corresponding to the core network of the evolved system can communicate with the core network of the evolved system, or can communicate with the core network of the pre-evolved system.
  • the access device involved in the present application may be implemented by improving an access device in an existing pre-evolution system, or may be a new access device, as long as at least two different connections can be implemented simultaneously.
  • the core network of the type may be connected to the terminal device corresponding to the at least two different core networks, which is not limited in this application.
  • FIG. 1 is a schematic diagram of a network access system provided by the present application.
  • the pre-evolution system uses an LTE system as an example; the evolved system takes an NR system as an example; can connect two different types of core networks, and can correspond to two different types of core networks.
  • the access device connected to the terminal device is implemented by the eNB of the LTE.
  • the core network of the Evolved Long Term Evolution Evolved NodeB (LTE) is EPC.
  • the core network of the system is called NR core network, New core network (NewCore), next generation core network (NG-Core) or 5G core network.
  • NewCore New core network
  • NG-Core next generation core network
  • 5G core network 5G core network.
  • the NR core network is taken as an example to terminate the terminal of the LTE system.
  • the device is called an LTE UE
  • the terminal device that can communicate with the NR core network through the eLTE eNB is called an eLTE UE
  • the eLTE eNB can connect to the EPC and the NR core network, and can connect with the LTE UE and the eLTE UE, and the LTE UE can
  • the ELTE communication can communicate with the NR core network or the EPC.
  • the EPC is connected, only the services supported by the LTE system can be initiated, and the new services supported by the NR core network cannot be initiated.
  • the eLTE eNB can simultaneously connect the EPC and the NR core network communication, and can be connected to the LTE UE and the eLTE UE, when the LTE UE or the eLTE UE requests to establish a connection with the core network through the eLTE eNB, the eLTE eNB needs to determine whether to use the LTE UE or The network device to which the eLTE UE is connected is determined by the eLTE eNB.
  • the type of the terminal device that needs to establish a connection with the core network ie, whether the terminal device is an LTE UE or an eLTE) UE
  • different types of terminal devices have the ability to connect to different types of core networks, determine which core network to connect to, connect to the EPC if the terminal device is an LTE UE, and connect to the NR core network if the terminal device is an eLTE UE.
  • the eLTE eNB may determine the type of the terminal device that needs to establish a connection with the core network by using, but not limited to, the following possible implementation manners.
  • a possible implementation manner is as follows: when the terminal device sends a certain message to the eLTE eNB (referred to as the first message in the present application), the indication information is used to indicate that the core network needs to be connected by adding the indication information to the first message.
  • the type of the terminal device is such that the eLTE eNB determines the type of the terminal device according to the indication information, thereby determining which core network the terminal device is to establish a connection with.
  • Another possible implementation manner is: when the terminal device establishes a connection with a different core network, the format of the first message sent by the terminal device to the eLTE eNB is different, and the eLTE eNB determines the type of the terminal device according to the format of the first message, and further determines Which core network the terminal device is to establish a connection with.
  • a further possible implementation manner is: when the terminal device establishes a connection with different core networks, the terminal device sends a first message to the eLTE eNB by using different transmission resources or transmission parameters, and the eLTE eNB determines the terminal according to different transmission resources or transmission parameters. The type of device, which in turn determines which core network the terminal device is to connect to.
  • the first message refers to a preamble sequence
  • different terminal device types are distinguished by different preamble sequences, namely: A part of the preamble sequence can only be used for the LTE UE, and a part of the preamble sequence can only be used for the eLTE UE.
  • the eLTE eNB knows the correspondence between the preamble sequence and the type of the terminal device in advance. The specific process is shown in Figure 2:
  • S201 The terminal device generates a preamble sequence.
  • the terminal device is an LTE UE
  • the preamble sequence available to the LTE UE is used
  • the preamble sequence available to the eLTE UE is used.
  • the terminal device sends a preamble sequence to the eLTE eNB.
  • the eLTE eNB determines the type of the terminal device according to the correspondence between the preamble sequence and the terminal device.
  • the correspondence between the preamble sequence and the terminal device includes: a correspondence between the preamble sequence and the eLTE UE;
  • the eLTE eNB determines that the preamble sequence is a preamble sequence corresponding to the eLTE UE, it determines that the terminal device is an eLTE eNB.
  • the eLTE eNB determines that the preamble sequence is a preamble sequence corresponding to the LTE UE, it determines that the terminal device is an LTE eNB.
  • the eLTE eNB determines the connected target core network according to the type of the terminal device.
  • the target core network is an EPC, and if the terminal device is an eLTE UE, the target core network is determined to be an NR core network.
  • the eLTE eNB determines the type of the terminal device according to the correspondence between the preamble sequence and the terminal device, and receives the preamble sequence sent by the terminal device, and determines which core network the terminal device is to establish with.
  • the connection enables, in the scenario where both the LTE system and the NR system exist, the access device accurately connects the terminal device to the target core network.
  • FIG. 3 is a schematic flowchart of a network access method according to Embodiment 2 of the present application.
  • the second embodiment is the same as the first embodiment, and the first message is a preamble sequence, and the difference is the eLTE UE in the second embodiment.
  • the preamble sequence that is available to the LTE UE is not differentiated.
  • the first indication information is added to the preamble sequence by the eLTE UE, indicating that the type of the terminal device is an eLTE UE, as follows:
  • S301 The terminal device generates a preamble sequence.
  • the generated preamble sequence includes the first indication information, where the first indication information is used to indicate that the type of the terminal device is an eLTE UE.
  • the generated preamble sequence does not carry the first indication information.
  • the terminal device sends a preamble sequence to the eLTE eNB.
  • the eLTE eNB determines the type of the terminal device according to whether the first indication information is included in the preamble sequence.
  • the determined terminal device is an eLTE UE
  • the terminal device If the first indicator information is not included in the preamble sequence sent by the terminal device, it is determined that the terminal device is an LTE UE.
  • the eLTE eNB determines the connected target core network according to the type of the terminal device.
  • the target core network is an EPC, and if the terminal device is an eLTE UE, the target core network is determined to be an NR core network.
  • the terminal device adds the first indication information to the preamble sequence to indicate that the type of the device on the terminal is an eLTE UE, and the eLTE eNB determines the type of the terminal device according to the first indication information in the preamble sequence, and further determines the terminal.
  • the access device can accurately connect the terminal device to the target core network.
  • the type of the terminal device may be distinguished by using different transmission resources (for example, time-frequency resources) when transmitting the first message.
  • the first message is a preamble sequence
  • the eLTE eNB determines the type of the terminal device according to the time-frequency resource of the preamble sequence and the correspondence between the time-frequency resource and the terminal device type, and further determines which core network the terminal device needs to establish a connection with.
  • the access device accurately connects the terminal device to the target core network.
  • the frame length, the subcarrier spacing, the Cyclic Prefix (CP) length, or the Transmission Time Interval (Transmission Time Interval) used by the first message may be transmitted.
  • the length of the TTI is different from the type of the terminal device, and the terminal device is connected to the core network. Therefore, in the scenario where the LTE system and the NR system exist simultaneously, the access device can accurately connect the terminal device. To the target core network.
  • the eLTE eNB further selects different RRC entities according to the type of the terminal device, and processes the RRC connection request message, the RRC connection setup message, or the RRC connection setup complete message through different RRC entities, and if the terminal device is determined. If the type is an eLTE UE, the RRC connection request message, the RRC connection setup message, or the RRC connection setup complete message is processed by the RRC entity corresponding to the NR core network; Determining that the type of the terminal device is an LTE UE, the RRC connection request message, the RRC connection setup message, or the RRC connection setup complete message is processed by the RRC entity corresponding to the EPC.
  • the first message in the fifth embodiment is an RRC connection request message
  • the second indication information is added to the RRC connection request message by the eLTE UE.
  • S401 The terminal device generates an RRC connection request message.
  • the generated RRC connection request message includes second indication information, where the second indication information is used to indicate that the type of the terminal device is an eLTE UE.
  • the generated RRC connection request message does not carry the second indication information.
  • the terminal device sends an RRC connection request message to the eLTE eNB.
  • the eLTE eNB determines the type of the terminal device according to whether the second indication information is included in the RRC connection request message.
  • the determined terminal device is an eLTE UE
  • the terminal device If the second indication information is not included in the RRC connection request message sent by the terminal device, it is determined that the terminal device is an LTE UE.
  • the eLTE eNB determines the connected target core network according to the type of the terminal device.
  • the target core network is an EPC, and if the terminal device is an eLTE UE, the target core network is determined to be an NR core network.
  • the process before the terminal device of the attaching process sends the RRC connection request message to the eLTE eNB, and the process after the eLTE eNB determines the target core network to access according to the type of the terminal device is the same as the prior art, and details are not described herein again.
  • the second indication information is added to the RRC connection request message by the terminal device, indicating that the type of the device on the terminal is an eLTE UE, and the eLTE eNB determines the type of the terminal device according to the second indication information in the RRC connection request message, and further It is determined in the scenario in which the LTE system and the NR system are present in the scenario in which the terminal device is connected to the core network, and the access device accurately connects the terminal device to the target core network.
  • FIG. 5 is a schematic flowchart of Embodiment 6 of the network access method of the present application.
  • the sixth embodiment is different from the fifth embodiment.
  • the sixth embodiment adds the third indication information to the RRC connection setup complete message to indicate the type of the terminal device.
  • the details are as follows:
  • S501 The terminal device generates an RRC connection setup complete message.
  • the generated RRC connection setup complete message includes third indication information, and the third indication information is used to indicate that the type of the terminal device is an eLTE UE.
  • the generated RRC connection setup complete message does not carry the third indication information.
  • the terminal device sends an RRC connection setup complete message to the eLTE eNB.
  • the eLTE eNB determines the type of the terminal device according to whether the third indication information is included in the RRC connection setup complete message.
  • the determined terminal device is an eLTE UE
  • the eLTE eNB determines the target core network to access according to the type of the terminal device.
  • the target core network is an EPC, and if the terminal device is an eLTE UE, the target core network is determined to be an NR core network.
  • the eLTE eNB processes the RRC Connection Setup Complete message through different RRC entities and sends an initial UE message to the core network.
  • the process before the terminal device of the attaching process sends the RRC connection setup complete message to the eLTE eNB, and the process after the eLTE eNB determines the target core network to access according to the type of the terminal device is the same as the prior art, and details are not described herein again.
  • the terminal device adds a third indication information in the RRC connection setup complete message, indicating that the type of the device on the terminal is an eLTE UE, and the eLTE eNB determines the type of the terminal device according to the third indication information in the RRC connection setup complete message. And determining which core network the terminal device is to establish with, so that the access device can accurately connect the terminal device to the target core network in the scenario where the LTE system and the NR system exist simultaneously.
  • the first message is an RRC connection setup complete message
  • the fourth indication information indicating the type of the terminal device is carried in the NAS message of the RRC connection setup complete message.
  • the RRC connection request message may be used to distinguish the type of the terminal device by using a different format; or the RRC setup complete message may be used to distinguish the type of the terminal device by using a different format; or, by using RRC
  • the NAS message in the setup completion message distinguishes the types of terminal devices in different formats.
  • the method before the eLTE eNB receives the first message sent by the terminal device, the method further includes: the eLTE eNB indicating to the terminal device that it has the capability of accessing different core networks, specifically,
  • the eLTE eNB sends capability indication information to the terminal device.
  • the capability indication information is used to indicate that the eLTE eNB has the capability of accessing the NR core network.
  • the eLTE eNB may send the capability indication information to the terminal device by using, but not limited to, the following manners;
  • the eLTE eNB sends the capability indication information to the terminal device, so that the terminal device learns that the eLTE eNB has the capability of accessing the NR core network and the EPC, thereby determining that the type of the terminal device is indicated by the first message, so that the eLTE eNB It is determined in the scenario in which the LTE system and the NR system are present in the scenario in which the terminal device is connected to the core network, and the access device accurately connects the terminal device to the target core network.
  • FIG. 6 is a schematic structural diagram of an embodiment of an access device according to the present application.
  • the access device of this embodiment is shown in FIG.
  • the receiver 601 is configured to receive the first message from the terminal device, where the first message is used to indicate that the terminal device is the first type of terminal device, where the first type of terminal device has a connection.
  • the capability of the first core network, the access device is connected to at least two different types of core networks, and the at least two different types of core networks include the first core network;
  • the processor 602 is configured to determine the type of the terminal device according to the first message.
  • the processor 602 is further configured to determine, according to the type of the terminal device, that the target core network accessed by the terminal device is the first core network.
  • the first message is a preamble sequence
  • the processor 602 is specifically configured to determine, according to a correspondence between the preamble sequence and the terminal device of the first type, that the type of the terminal device is the first type.
  • the first message is a preamble sequence
  • the preamble sequence includes first indication information, where the first indication information is used to indicate that the type of the terminal device is the first type.
  • the processor 602 is specifically configured to determine, according to the time-frequency resource of the preamble sequence, and the correspondence between the time-frequency resource and the terminal device of the first type, that the type of the terminal device is the first type.
  • the processor 602 is specifically configured to determine, according to the frame length, the subcarrier spacing, the cyclic prefix CP length, or the transmission time interval TTI length used for transmitting the first message, the type of the terminal device is the first type.
  • the first message is a radio resource control RRC connection request message
  • the RRC connection request message includes second indication information, where the second indication information is used to indicate the type of the terminal device.
  • the first message is an RRC connection setup complete message
  • the RRC connection setup complete message includes third indication information, where the third indication information is used to indicate that the type of the terminal device is the first type.
  • the first message is an RRC connection setup complete message
  • the RRC connection setup complete message includes a non-access stratum NAS message
  • the NAS message includes fourth indication information
  • the fourth indication information is used to indicate the type of the terminal device. For the first type.
  • the first message is an RRC connection request message or an RRC connection setup complete message
  • the processor 602 is specifically configured to determine, according to the format of the RRC connection request message or the RRC connection setup complete message, that the type of the terminal device is the first type.
  • the first message is an RRC connection setup complete message
  • the processor 602 is specifically configured to determine, according to the format of the NAS message in the RRC connection setup complete message, that the type of the terminal device is the first type.
  • the method further includes:
  • the transmitter 603 is configured to send capability indication information to the terminal device, where the capability indication information is used to indicate that the access device has the capability of accessing the first core network.
  • the processor in the access device of the embodiment shown in FIG. 6 is configured to support the access device to perform a corresponding function in the above network access method.
  • the receiver or the transmitter is configured to support communication between the access device and the terminal device and the core network, and send information or instructions involved in the network access method to the terminal device or the core network, and implement the principle, technical effect and method implementation.
  • the example is similar and will not be described here.
  • FIG. 7 is a schematic structural diagram of an embodiment of a terminal device according to the present application.
  • the terminal device in this embodiment includes a processor 701 and a transmitter 702, where the processor 701 is configured to generate a first message, and the transmitter 702 is configured to send to the access device. a first message, where the first message is used to indicate that the terminal device is the first type of terminal device, where the first type is terminated.
  • the end device has the capability of accessing the first core network, the access device is connected to at least two different types of core networks, and the at least two different core networks include the first core network.
  • the processor 701 is further configured to determine a format of the first message according to the target core network to be accessed.
  • the processor 701 is further configured to determine that the access device has the capability of accessing the first core network.
  • the method further includes:
  • the receiver 703 is configured to receive a broadcast message, where the broadcast message includes capability indication information, where the capability indication information is used to indicate that the access device has the capability of accessing the first core network;
  • the receiver 703 is configured to receive random access response information, where the random access response information includes capability indication information.
  • the receiver 703 is configured to receive a radio resource control RRC connection setup message, where the RRC connection setup message includes capability indication information.
  • the first message is a preamble sequence
  • the processor 701 is specifically configured to determine a preamble sequence according to a correspondence between the preamble sequence and the first type of terminal device.
  • the first message is a preamble sequence
  • the preamble sequence includes first indication information, where the first indication information is used to indicate that the type of the terminal device is the first type.
  • the processor 701 is specifically configured to determine, according to the correspondence between the time-frequency resource and the terminal device of the first type, the time-frequency resource that sends the preamble sequence to the access device.
  • the transmitter 702 is specifically configured to transmit the first message according to a frame length, a subcarrier interval, a cyclic prefix CP length, or a transmission time interval TTI length adopted by the first message of the first type of terminal device.
  • the first message is a radio resource control RRC connection request message
  • the RRC connection request message includes second indication information, where the second indication information is used to indicate that the type of the terminal device is the first type.
  • the first message is an RRC connection setup complete message
  • the RRC connection setup complete message includes third indication information, where the third indication information is used to indicate that the type of the terminal device is the first type.
  • the first message is an RRC connection setup complete message
  • the RRC connection setup complete message includes a non-access stratum NAS message
  • the NAS message includes fourth indication information
  • the fourth indication information is used to indicate the type of the terminal device. For the first type.
  • the first message is an RRC connection request message or an RRC connection setup complete message
  • the processor 701 is specifically configured to generate a first message according to a format of an RRC connection request message or an RRC connection setup complete message of the target core network to be accessed.
  • the first message is an RRC connection setup complete message
  • the processor 701 is specifically configured to generate a first message according to a format of the NAS message in the RRC connection setup complete message of the target core network to be accessed.
  • the processor in the access device of the embodiment shown in FIG. 7 is configured to support the terminal device to perform a corresponding function in the above network access method.
  • the receiver or the transmitter is configured to support communication between the terminal device and the access device, and send the information or instructions involved in the network access method to the access device, and the implementation principle and technical effect thereof The method embodiment is similar and will not be described here.
  • the present application further provides an access device, which has the function of implementing the behavior of the access device in the foregoing access method.
  • the functions can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the access device includes multiple function modules, and is used to implement any one of the network access methods in the foregoing first aspect, so that the access device determines the target core network to which the terminal device is connected, thereby enabling LTE to exist at the same time.
  • the access device accurately connects the terminal device to the target core network.
  • the implementation principle and technical effects are similar to the method embodiments, and are not described here.
  • the application provides a terminal device, which has a function of implementing the behavior of the terminal device in the foregoing access method.
  • the functions can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the access device includes a plurality of functional modules, which are used to implement the network access method of any one of the foregoing second aspects, by sending a message to the access device, indicating the type of the terminal device, so that the access device can
  • the type of the terminal device determines the target core network to which the terminal device is connected, so that in the scenario where the LTE system and the NR system exist simultaneously, the access device accurately connects the terminal device to the target core network.
  • the implementation principle and technical effects are similar to the method embodiments, and are not described here.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the program when executed, performs the steps including the foregoing method embodiments; and the foregoing storage medium includes various media that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请提供一种网络接入方法、接入设备和终端设备,其中,接入设备连接至少两个不同类型的核心网,当终端设备要连接核心网时,向接入设备发送用于指示终端设备类型的第一消息,接入设备根据第一消息确定终端设备的类型,根据终端设备的类型确定终端设备连接的目标核心网,实现接入设备准确的将终端设备连接至目标核心网。

Description

网络接入方法、接入设备和终端设备
本申请要求于2016年08月22日提交中国专利局、申请号为201610702579.5、申请名称为“网络接入方法、接入设备和终端设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术,尤其涉及一种网络接入方法、接入设备和终端设备。
背景技术
随着无线通信技术的不断发展,在长期演进(Long Term Evolution,简称:LTE)技术之后出现了新无线接入技术(New Radio Access Technology,简称:NR)。
在NR***中,包括NR站点和NR核心网;其中,NR站点与LTE***中的演进型基站(Evolved NodeB,简称:eNB)相比,提供不一样的空口,例如:更短的传输时间间隔(Transmission Time Interval,简称:TTI),更大的带宽等;NR***的NR核心网与LTE***中的演进分组核心网(Evolved Packet Core,简称:EPC)相比,能够支持更多的业务类型。现有技术中,LTE的终端设备通过eNB接入到EPC,NR的终端设备通过NR站点接入到NR核心网,然而,由于网络部署的成本及终端设备的更换成本等问题,需要从现有的LTE***向NR***平滑演进,即:会出现LTE***和NR***同时存在的场景。
然而,在同时存在LTE***和NR***的场景中,采用现有技术的方法,接入设备无法确定将终端设备连接至哪个***的核心网。
发明内容
本申请提供一种网络接入方法、接入设备和终端设备,以解决现有技术中在同时存在LTE***和NR***的场景中,接入设备无法确定将终端设备连接至哪个***的核心网的问题。
第一方面,本申请提供一种网络接入方法,包括:
接入设备连接至少两个不同类型的核心网,不同类型的终端设备具有连接至不同类型的核心网的能力,当终端设备要连接核心网时,向接入设备发送用于指示终端设备类型的第一消息,接入设备根据第一消息确定终端设备的类型,进而,根据第一消息确定终端设备的类型,根据终端设备的类型,确定终端设备连接的目标核心网,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
在一种可能的设计中,所述第一消息为前导码序列;
所述接入设备根据所述第一消息,确定所述终端设备的类型为第一类型,包括:
所述接入设备根据所述前导码序列与所述第一类型的终端设备的对应关系,确定所述终端设备的类型为第一类型。
在一种可能的设计中,所述第一消息为前导码序列,所述前导码序列中包含第一指示信息,所述第一指示信息用于指示所述终端设备的类型为第一类型。
在一种可能的设计中,所述接入设备根据所述前导码序列与所述第一类型的终端设备的对应关系,确定所述终端设备的类型为第一类型,包括:
所述接入设备根据所述前导码序列的时频资源,以及所述时频资源与所述第一类型的终端设备的对应关系,确定所述终端设备的类型为第一类型。
在一种可能的设计中,所述接入设备根据所述第一消息,确定所述终端设备的类型为第一类型,包括:
所述接入设备根据传输所述第一消息所采用的帧长度、子载波间隔、循环前缀CP长度或者传输时间间隔TTI长度确定所述终端设备的类型为第一类型。
在一种可能的设计中,所述第一消息为无线资源控制RRC连接请求消息,所述RRC连接请求消息中包含第二指示信息,所述第二指示信息用于指示所述终端设备的类型。
在一种可能的设计中,所述第一消息为RRC连接建立完成消息,所述RRC连接建立完成消息中包含第三指示信息,所述第三指示信息用于指示所述终端设备的类型为第一类型。
在一种可能的设计中,所述第一消息为RRC连接建立完成消息,所述RRC连接建立完成消息中包含非接入层NAS消息,所述NAS消息中包含第四指示信息,所述第四指示信息用于指示所述终端设备的类型为第一类型。
在一种可能的设计中,所述第一消息为RRC连接请求消息或者RRC连接建立完成消息;
所述接入设备根据所述第一消息,确定所述终端设备的类型为第一类型,包括:
所述接入设备根据所述RRC连接请求消息或者RRC连接建立完成消息的格式,确定所述终端设备的类型为第一类型。
在一种可能的设计中,所述第一消息为RRC连接建立完成消息;
所述接入设备根据所述第一消息,确定所述终端设备的类型为第一类型,包括:
所述接入设备根据所述RRC连接建立完成消息中的NAS消息的格式,确定所述终端设备的类型为第一类型。
在一种可能的设计中,所述接入设备接收终端设备发送的第一消息之前,还包括:
所述接入设备向所述终端设备发送能力指示信息,所述能力指示信息用于指示所述接入设备具有接入所述第一核心网的能力。
第二方面,本申请提供一种网络接入方法,包括:
终端设备生成第一消息;
所述终端设备向接入设备发送所述第一消息,所述第一消息用于指示终端设备为第一类型的终端设备,其中,所述第一类型的终端设备具备接入第一核心网的能力,所述接入设备连接至少两个不同类型的核心网,所述至少两个不同的核心网包括所述 第一核心网。
在一种可能的设计中,所述终端设备生成第一消息之前,还包括:
所述终端设备根据待接入的目标核心网,确定所述第一消息的格式。
在一种可能的设计中,所述终端设备向接入设备发送第一消息之前,还包括:
所述终端设备确定所述接入设备具有接入所述第一核心网的能力。
在一种可能的设计中,所述终端设备确定所述接入设备具有接入第一核心网的能力之前,还包括:
所述终端设备接收广播消息,所述广播消息中包含能力指示信息,所述能力指示信息用于指示所述接入设备具有接入第一核心网的能力;
或者,
所述终端设备接收随机接入响应信息,所述随机接入响应信息中包含所述能力指示信息;
或者,
所述终端设备接收无线资源控制RRC连接建立消息,所述RRC连接建立消息中包含所述能力指示信息。
在一种可能的设计中,所述第一消息为前导码序列;
所述终端设备生成第一消息,包括:
所述终端设备根据所述前导码序列与所述第一类型的终端设备的对应关系,确定所述前导码序列。
在一种可能的设计中,所述第一消息为前导码序列,所述前导码序列中包含第一指示信息,所述第一指示信息用于指示所述终端设备的类型为第一类型。
在一种可能的设计中,所述终端设备根据所述前导码序列与所述第一类型的终端设备的对应关系,确定所述前导码序列,包括:
所述终端设备根据时频资源与所述第一类型的终端设备的对应关系,确定向接入设备发送所述前导码序列的时频资源。
在一种可能的设计中,所述终端设备向接入设备发送第一消息,包括:
所述终端设备根据传输所述第一类型的终端设备的所述第一消息所采用的帧长度、子载波间隔、循环前缀CP长度或者传输时间间隔TTI长度传输所述第一消息。
在一种可能的设计中,所述第一消息为无线资源控制RRC连接请求消息,所述RRC连接请求消息中包含第二指示信息,所述第二指示信息用于指示所述终端设备的类型为第一类型。
在一种可能的设计中,所述第一消息为RRC连接建立完成消息,所述RRC连接建立完成消息中包含第三指示信息,所述第三指示信息用于指示所述终端设备的类型为第一类型。
在一种可能的设计中,所述第一消息为RRC连接建立完成消息,所述RRC连接建立完成消息中包含非接入层NAS消息,所述NAS消息中包含第四指示信息,所述第四指示信息用于指示所述终端设备的类型为第一类型。
在一种可能的设计中,所述第一消息为RRC连接请求消息或者RRC连接建立完成消息;
所述终端设备生成第一消息,包括:
所述终端设备根据待接入的目标核心网的RRC连接请求消息或者RRC连接建立完成消息的格式,生成第一消息。
在一种可能的设计中,所述第一消息为RRC连接建立完成消息;
所述终端设备生成第一消息,包括:
所述终端设备根据待接入的目标核心网的RRC连接建立完成消息中的NAS消息的格式,生成第一消息。
第三方面,为了实现上述第一方面的网络接入方法,本申请提供了一种接入设备,该接入设备具有实现上述接入方法中接入设备行为的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在第三方面的一种可能的实现方式中,该接入设备包括多个功能模块,用于实现上述第一方面中的任一种网络接入方法,使得接入设备确定终端设备连接的目标核心网,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
在第三方面的一种可能的实现方式中,接入设备的结构中包括处理器和收发器,所述处理器被配置为支持接入设备执行上述网络接入方法中相应的功能。所述接收器或者发送器用于支持接入设备与终端设备和核心网之间的通信,向终端设备或核心网发送上述网络接入方法中所涉及的信息或者指令。接入设备中还可以包括存储器,所述存储器用于与处理器耦合,其保存接入设备必要的程序指令和数据。
第四方面,为了实现上述第一方面的网络接入方法,本申请提供了一种终端设备,该终端设备具有实现上述接入方法中终端设备行为的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在第四方面的一种可能的实现方式中,该终端设备包括多个功能模块,用于实现上述第二方面中的任一种网络接入方法,通过向接入设备发发送消息,指示终端设备的类型,使接入设备能够根据终端设备的类型确定终端设备连接的目标核心网,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
在第四方面的一种可能的实现方式中,终端设备的结构中包括处理器和收发器,所述处理器被配置为支持终端设备执行上述网络接入方法中相应的功能。所述接收器或者发送器用于支持终端设备与接入设备之间的通信,向接入设备发送上述网络接入方法中所涉及的信息或者指令。终端设备中还可以包括存储器,所述存储器用于与处理器耦合,其保存接入设备必要的程序指令和数据。
附图说明
图1为本申请提供的网络接入***的一种示意图;
图2为本申请网络接入方法实施例一的流程示意图;
图3为本申请网络接入方法实施例二的流程示意图;
图4为本申请网络接入方法实施例五的流程示意图;
图5为本申请网络接入方法实施例六的流程示意图;
图6为本申请接入设备实施例的结构示意图;
图7为本申请终端设备实施例的结构示意图。
具体实施方式
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换,以便这里描述的本申请的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外,术语“包括”和“具有”以及他们的任何变形,意图在于覆盖不排他的包含,例如,包含了一系列步骤或单元的过程、方法、***、产品或设备不必限于清楚地列出的那些步骤或单元,而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
随着无线通信技术的不断发展,无线通信***也在不断的演进,为了从演进前的***向演进后的***平滑过渡,本申请提供一种接入设备,该接入设备可以实现同时连接至少两个不同类型的核心网,并且,可以同时与上述至少两个不同的核心网对应的终端设备连接,其中,演进前的***的核心网对应的终端设备只能与演进前的***的核心网进行通信,演进后的***的核心网对应的终端上设备可以与演进后的***的核心网进行通信,也可以与演进前的***的核心网进行通信。本申请所涉及的接入设备可以是通过对现有的演进前的***中的接入设备进行改进而实现的,也可以是一种新的接入设备,只要能够实现同时连接至少两个不同类型的核心网,并且可以同时与上述至少两个不同的核心网对应的终端设备连接即可,对此,本申请不作限制。
下述各实施例以图1所示的场景为例,图1为本申请提供的网络接入***的一种示意图。其中,在图1中,上述演进前的***以LTE***为例;演进后的***以NR***为例;能够连接两个不同类型的核心网,并且,能够与两个不同类型的核心网对应的终端设备连接的接入设备,以通过LTE的eNB进行改进而实现的为例,称为演进LTE eNB(Evolved Long Term Evolution Evolved NodeB,简称:eLTE eNB;LTE)的核心网为EPC,将NR***的核心网称为NR核心网、新核心网(NewCore)、下一代核心网(NG-Core)或者5G核心网等,本申请为了便于描述,以NR核心网为例,将LTE***的终端设备称为LTE UE,将能够通过eLTE eNB与NR核心网进行通信的终端设备称为eLTE UE,eLTE eNB可以连接EPC和NR核心网,并且,可以与LTE UE和eLTE UE连接,LTE UE可以与EPC通信;eLTE UE即可以与NR核心网通信,也可以与EPC通信,在连接EPC时,只能发起LTE***支持的业务,不能发起NR核心网支持的新业务。
由于eLTE eNB可以同时连接EPC和NR核心网通,以及,可以与LTE UE和eLTE UE连接,因此,在LTE UE或者eLTE UE通过eLTE eNB请求与核心网建立连接时,eLTE eNB需要确定将LTE UE或者eLTE UE连接至到哪个核心网,本申请通过eLTE eNB确定需要与核心网建立连接的终端设备的类型(即终端设备是LTE UE还是eLTE  UE),不同类型的终端设备具有连接至不同类型的核心网的能力,确定连接至哪个核心网,如果终端设备是LTE UE则连接至EPC,如果终端设备是eLTE UE则连接至NR核心网。
eLTE eNB可以通过但不限于如下可能的实现方式,确定需要与核心网建立连接的终端设备的类型。
其中,一种可能的实现方式为:终端设备向eLTE eNB发送某个消息时(本申请称为第一消息),通过在第一消息中增加指示信息,该指示信息用于指示需要连接核心网的终端设备的类型,以使eLTE eNB根据该指示信息确定终端设备的类型,进而确定终端设备要与哪个核心网建立连接。
另一种可能的实现方式为:终端设备与不同的核心网建立连接时,终端设备向eLTE eNB发送的第一消息的格式不同,eLTE eNB根据第一消息的格式确定终端设备的类型,进而确定终端设备要与哪个核心网建立连接。
再一种可能的实现方式为:终端设备与不同的核心网建立连接时,终端设备采用不同的传输资源或传输参数向eLTE eNB发送第一消息,eLTE eNB根据不同的传输资源或传输参数确定终端设备的类型,进而确定终端设备要与哪个核心网建立连接。
下面以具体地实施例对本申请的技术方案进行详细说明。下面这几个具体的实施例可以相互结合,对于相同或相似的概念或过程可能在某些实施例不再赘述。
图2为本申请网络接入方法实施例一的流程示意图,如图2所示,本实施例中,第一消息指前导码序列,通过不同的前导码序列区分不同的终端设备类型,即:一部分前导码序列只能用于LTE UE,一部分前导码序列只能用于eLTE UE,eLTE eNB预先获知前导码序列与终端设备的类型的对应关系;具体流程如图2所示:
S201:终端设备生成前导码序列。
例如:终端设备为LTE UE时,采用LTE UE可用的前导码序列;
终端设备为eLTE UE时,采用eLTE UE可用的前导码序列。
S202:终端设备向eLTE eNB发送前导码序列。
S203:eLTE eNB根据所述前导码序列与终端设备的对应关系,确定终端设备的类型。
其中,前导码序列与终端设备的对应关系,包括:前导码序列与eLTE UE的对应关系;
eLTE eNB若确定前导码序列为eLTE UE对应的前导码序列,则确定终端设备为eLTE eNB。
eLTE eNB若确定前导码序列为LTE UE对应的前导码序列,则确定终端设备为LTE eNB。
S204:eLTE eNB根据终端设备的类型,确定连接的目标核心网。
若终端设备是LTE UE,则确定目标核心网为EPC,若终端设备是eLTE UE则确定目标核心网为NR核心网。
附着过程的后续流程与现有技术相同,此处不再赘述。
本实施例,eLTE eNB根据前导码序列与终端设备的对应关系,以及接收到终端设备发送的前导码序列,确定终端设备的类型,进而确定终端设备要与哪个核心网建立 连接,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
图3为本申请网络接入方法实施例二的流程示意图,如图3所示,实施例二与实施例一相同的是第一消息为前导码序列,不同的是实施例二中eLTE UE和LTE UE可用的前导码序列不作区分,通过eLTE UE在前导码序列中增加第一指示信息,指示终端设备的类型为eLTE UE,具体如下:
S301:终端设备生成前导码序列。
例如:终端设备为eLTE UE时,生成的前导码序列中包含第一指示信息,第一指示信息用于指示终端设备的类型为eLTE UE。
终端设备为LTE UE时,生成的前导码序列中不带第一指示信息。
S302:终端设备向eLTE eNB发送前导码序列。
S303:eLTE eNB根据前导码序列中是否包含第一指示信息,确定终端设备的类型。
若终端设备发送的前导码序列中包含第一指示信息,则确定的终端设备为eLTE UE;
若终端设备发送的前导码序列中未包含第一指示信息,则确定终端设备为LTE UE。
S304:eLTE eNB根据终端设备的类型,确定连接的目标核心网。
若终端设备是LTE UE,则确定目标核心网为EPC,若终端设备是eLTE UE则确定目标核心网为NR核心网。
附着过程的后续流程与现有技术相同,此处不再赘述。
本实施例,通过终端设备在前导码序列中增加第一指示信息,指示终端上设备的类型为eLTE UE,eLTE eNB根据前导码序列中的第一指示信息,确定终端设备的类型,进而确定终端设备要与哪个核心网建立连接,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
可选地,作为本申请的另一个实施方式,可以通过传输第一消息时采用不同的传输资源(例如:时频资源),区分终端设备的类型。其中,第一消息为前导码序列,eLTE eNB根据前导码序列的时频资源,以及时频资源与终端设备类型的对应关系,确定终端设备的类型,进而确定终端设备要与哪个核心网建立连接,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
可选地,作为本申请的另一个实施方式,可以通过传输第一消息所采用的帧长度、子载波间隔、循环前缀(Cyclic Prefix,简称:CP)长度或者传输时间间隔(Transmission Time Interval,简称:TTI)长度等区分不同的终端设备的类型,进而确定终端设备要与哪个核心网建立连接,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
在上述各实施例中,还包括eLTE eNB根据终端设备的类型选择不同的RRC实体,通过不同的RRC实体处理RRC连接请求消息、RRC连接建立消息或者RRC连接建立完成消息等,若确定终端设备的类型为eLTE UE,则通过NR核心网对应的RRC实体处理上述RRC连接请求消息、RRC连接建立消息或者RRC连接建立完成消息;若 确定终端设备的类型为LTE UE,则通过EPC对应的RRC实体处理上述RRC连接请求消息、RRC连接建立消息或者RRC连接建立完成消息。
图4为本申请网络接入方法实施例五的流程示意图,如图4所示实施例五中的第一消息为RRC连接请求消息,通过eLTE UE在RRC连接请求消息中增加第二指示信息,指示终端设备的类型为eLTE UE,具体如下:
S401:终端设备生成RRC连接请求消息。
例如:终端设备为eLTE UE时,生成的RRC连接请求消息中包含第二指示信息,第二指示信息用于指示终端设备的类型为eLTE UE。
终端设备为LTE UE时,生成的RRC连接请求消息不带第二指示信息。
S402:终端设备向eLTE eNB发送RRC连接请求消息。
S403:eLTE eNB根据所述RRC连接请求消息中是否包含第二指示信息,确定终端设备的类型。
若终端设备发送的RRC连接请求消息中包含第二指示信息,则确定的终端设备为eLTE UE;
若终端设备发送的RRC连接请求消息中未包含第二指示信息,则确定终端设备为LTE UE。
S404:eLTE eNB根据终端设备的类型,确定连接的目标核心网。
若终端设备是LTE UE,则确定目标核心网为EPC,若终端设备是eLTE UE则确定目标核心网为NR核心网。
附着过程的终端设备向eLTE eNB发送RRC连接请求消息之前的流程,与eLTE eNB根据终端设备的类型,确定接入的目标核心网之后的流程与现有技术相同,此处不再赘述。
本实施例,通过终端设备在RRC连接请求消息中增加第二指示信息,指示终端上设备的类型为eLTE UE,eLTE eNB根据RRC连接请求消息中的第二指示信息,确定终端设备的类型,进而确定终端设备要与哪个核心网建立连接,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
图5为本申请网络接入方法实施例六的流程示意图,实施例六与实施例五不同的是,实施例六是通过在RRC连接建立完成消息中增加第三指示信息,指示终端设备的类型为eLTE UE,具体如下:
S501:终端设备生成RRC连接建立完成消息。
例如:终端设备为eLTE UE时,生成的RRC连接建立完成消息中包含第三指示信息,第三指示信息用于指示终端设备的类型为eLTE UE。
终端设备为LTE UE时,生成的RRC连接建立完成消息不带第三指示信息。
S502:终端设备向eLTE eNB发送RRC连接建立完成消息。
S503:eLTE eNB根据所述RRC连接建立完成消息中是否包含第三指示信息,确定终端设备的类型。
若终端设备发送的RRC连接建立完成消息中包含第三指示信息,则确定的终端设备为eLTE UE;
若终端设备发送的RRC连接建立完成消息中未包含第三指示信息,则确定终端设 备为LTE UE。
S504:eLTE eNB根据终端设备的类型,确定接入的目标核心网。
若终端设备是LTE UE,则确定目标核心网为EPC,若终端设备是eLTE UE则确定目标核心网为NR核心网。
eLTE eNB通过不同的RRC实体处理RRC连接建立完成消息,并向核心网发送初始UE消息。
附着过程的终端设备向eLTE eNB发送RRC连接建立完成消息之前的流程,与eLTE eNB根据终端设备的类型,确定接入的目标核心网之后的流程与现有技术相同,此处不再赘述。
本实施例,通过终端设备在RRC连接建立完成消息中增加第三指示信息,指示终端上设备的类型为eLTE UE,eLTE eNB根据RRC连接建立完成消息中的第三指示信息,确定终端设备的类型,进而确定终端设备要与哪个核心网建立连接,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
可选地,作为本申请的另一个实施方式,可以是第一消息为RRC连接建立完成消息,用于指示终端设备的类型的第四指示信息携带在RRC连接建立完成消息的NAS消息中。
可选地,作为本申请的另一个实施方式,可以通过RRC连接请求消息采用不同的格式区分终端设备的类型;或者,通过RRC建立完成消息采用不同的格式区分终端设备的类型;或者,通过RRC建立完成消息中的NAS消息采用不同的格式区分终端设备的类型。
在上述实施各实施例中,在eLTE eNB接收终端设备发送的第一消息之前,进一步地,还包括:eLTE eNB向终端设备指示其具有接入不同的核心网的能力,具体地,
eLTE eNB向终端设备发送能力指示信息。
其中,能力指示信息用于指示eLTE eNB具有接入NR核心网的能力。
具体地,eLTE eNB可以通过但不限于如下方式向终端设备发送能力指示信息;
其中,一种可能的实现方式为:
发送广播消息,所述广播消息中包含能力指示信息;
另一种可能的实现方式为:
向终端设备发送随机接入响应信息,所述随机接入响应信息中包含所述能力指示信息;
再一种可能的实现方式为:
向终端设备发送RRC连接建立消息,所述RRC连接建立消息中包含所述能力指示信息。
本实施例,通过eLTE eNB向终端设备发送能力指示信息,以使终端设备获知eLTE eNB具有接入NR核心网和EPC的能力,从而,确定通过第一消息指示终端设备的类型,以使eLTE eNB确定终端设备要与哪个核心网建立连接,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。
图6为本申请接入设备实施例的结构示意图,如图6所示,本实施例的接入设备 包括接收器601、处理器602,其中,接收器601用于从终端设备接收第一消息,第一消息用于指示终端设备为第一类型的终端设备,其中,第一类型的终端设备具有接入第一核心网的能力,接入设备连接至少两个不同类型的核心网,至少两个不同类型的核心网包括第一核心网;处理器602用于根据第一消息,确定终端设备的类型为第一类型;处理器602还用于根据终端设备的类型,确定终端设备接入的目标核心网为第一核心网。
在上述实施例中,第一消息为前导码序列;
处理器602具体用于根据前导码序列与第一类型的终端设备的对应关系,确定终端设备的类型为第一类型。
在上述实施例中,第一消息为前导码序列,前导码序列中包含第一指示信息,第一指示信息用于指示终端设备的类型为第一类型。
在上述实施例中,处理器602具体用于根据前导码序列的时频资源,以及时频资源与第一类型的终端设备的对应关系,确定终端设备的类型为第一类型。
在上述实施例中,处理器602具体用于根据传输第一消息所采用的帧长度、子载波间隔、循环前缀CP长度或者传输时间间隔TTI长度确定终端设备的类型为第一类型。
在上述实施例中,第一消息为无线资源控制RRC连接请求消息,RRC连接请求消息中包含第二指示信息,第二指示信息用于指示终端设备的类型。
在上述实施例中,第一消息为RRC连接建立完成消息,RRC连接建立完成消息中包含第三指示信息,第三指示信息用于指示终端设备的类型为第一类型。
在上述实施例中,第一消息为RRC连接建立完成消息,RRC连接建立完成消息中包含非接入层NAS消息,NAS消息中包含第四指示信息,第四指示信息用于指示终端设备的类型为第一类型。
在上述实施例中,第一消息为RRC连接请求消息或者RRC连接建立完成消息;
处理器602具体用于根据RRC连接请求消息或者RRC连接建立完成消息的格式,确定终端设备的类型为第一类型。
在上述实施例中,第一消息为RRC连接建立完成消息;
处理器602具体用于根据RRC连接建立完成消息中的NAS消息的格式,确定终端设备的类型为第一类型。
在上述实施例中,还包括:
发送器603用于向终端设备发送能力指示信息,能力指示信息用于指示接入设备具有接入第一核心网的能力。
图6所示实施例的接入设备中处理器被配置为支持接入设备执行上述网络接入方法中相应的功能。接收器或者发送器用于支持接入设备与终端设备和核心网之间的通信,向终端设备或核心网发送上述网络接入方法中所涉及的信息或者指令,其实现原理和技术效果与方法实施例类似,此处不再赘述。
图7为本申请终端设备实施例的结构示意图,本实施例的终端设备包括处理器701、发送器702,其中,处理器701用于生成第一消息;发送器702用于向接入设备发送第一消息,第一消息用于指示终端设备为第一类型的终端设备,其中,第一类型的终 端设备具备接入第一核心网的能力,接入设备连接至少两个不同类型的核心网,至少两个不同的核心网包括第一核心网。
在上述实施例中,处理器701还用于根据待接入的目标核心网,确定第一消息的格式。
在上述实施例中,处理器701还用于确定接入设备具有接入第一核心网的能力。
在上述实施例中,还包括:
接收器703用于接收广播消息,广播消息中包含能力指示信息,能力指示信息用于指示接入设备具有接入第一核心网的能力;
或者,
接收器703用于接收随机接入响应信息,随机接入响应信息中包含能力指示信息;
或者,
接收器703用于接收无线资源控制RRC连接建立消息,RRC连接建立消息中包含能力指示信息。
在上述实施例中,第一消息为前导码序列;
处理器701具体用于根据前导码序列与第一类型的终端设备的对应关系,确定前导码序列。
在上述实施例中,第一消息为前导码序列,前导码序列中包含第一指示信息,第一指示信息用于指示终端设备的类型为第一类型。
在上述实施例中,处理器701具体用于根据时频资源与第一类型的终端设备的对应关系,确定向接入设备发送前导码序列的时频资源。
在上述实施例中,发送器702具体用于根据传输第一类型的终端设备的第一消息所采用的帧长度、子载波间隔、循环前缀CP长度或者传输时间间隔TTI长度传输第一消息。
在上述实施例中,第一消息为无线资源控制RRC连接请求消息,RRC连接请求消息中包含第二指示信息,第二指示信息用于指示终端设备的类型为第一类型。
在上述实施例中,第一消息为RRC连接建立完成消息,RRC连接建立完成消息中包含第三指示信息,第三指示信息用于指示终端设备的类型为第一类型。
在上述实施例中,第一消息为RRC连接建立完成消息,RRC连接建立完成消息中包含非接入层NAS消息,NAS消息中包含第四指示信息,第四指示信息用于指示终端设备的类型为第一类型。
在上述实施例中,第一消息为RRC连接请求消息或者RRC连接建立完成消息;
处理器701具体用于根据待接入的目标核心网的RRC连接请求消息或者RRC连接建立完成消息的格式,生成第一消息。
在上述实施例中,第一消息为RRC连接建立完成消息;
处理器701具体用于根据待接入的目标核心网的RRC连接建立完成消息中的NAS消息的格式,生成第一消息。
图7所示实施例的接入设备中处理器被配置为支持终端设备执行上述网络接入方法中相应的功能。接收器或者发送器用于支持终端设备与接入设备之间的通信,向接入设备发送上述网络接入方法中所涉及的信息或者指令,其实现原理和技术效果与方 法实施例类似,此处不再赘述。
为了实现上述网络接入方法,本申请还提供了一种接入设备,该接入设备具有实现上述接入方法中接入设备行为的功能。功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
其中,该接入设备包括多个功能模块,用于实现上述第一方面中的任一种网络接入方法,使得接入设备确定终端设备连接的目标核心网,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。其实现原理和技术效果与方法实施例类似,此处不再赘述。
为了实现上述第一方面的网络接入方法,本申请提供了一种终端设备,该终端设备具有实现上述接入方法中终端设备行为的功能。功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
其中,该接入设备包括多个功能模块,用于实现上述第二方面中的任一种网络接入方法,通过向接入设备发发送消息,指示终端设备的类型,使接入设备能够根据终端设备的类型确定终端设备连接的目标核心网,从而,能够实现在同时存在LTE***和NR***的场景中,接入设备准确的将终端设备连接至目标核心网。其实现原理和技术效果与方法实施例类似,此处不再赘述。
本领域普通技术人员可以理解:实现上述各方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成。前述的程序可以存储于一计算机可读取存储介质中。该程序在执行时,执行包括上述各方法实施例的步骤;而前述的存储介质包括:ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是:以上各实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述各实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分或者全部技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (30)

  1. 一种网络接入方法,其特征在于,包括:
    接入设备从终端设备接收第一消息,所述第一消息用于指示所述终端设备为第一类型的终端设备,其中,所述第一类型的终端设备具有接入第一核心网的能力,所述接入设备连接至少两个不同类型的核心网,所述至少两个不同类型的核心网包括所述第一核心网;
    所述接入设备根据所述第一消息,确定所述终端设备的类型为第一类型;
    所述接入设备根据所述终端设备的类型,确定所述终端设备接入的目标核心网为所述第一核心网。
  2. 根据权利要求1所述的方法,其特征在于,所述第一消息为前导码序列;
    所述接入设备根据所述第一消息,确定所述终端设备的类型为第一类型,包括:
    所述接入设备根据所述前导码序列与所述第一类型的终端设备的对应关系,确定所述终端设备的类型为第一类型。
  3. 根据权利要求1所述的方法,其特征在于,所述第一消息为前导码序列,所述前导码序列中包含第一指示信息,所述第一指示信息用于指示所述终端设备的类型为第一类型。
  4. 根据权利要求2所述的方法,其特征在于,所述接入设备根据所述前导码序列与所述第一类型的终端设备的对应关系,确定所述终端设备的类型为第一类型,包括:
    所述接入设备根据所述前导码序列的时频资源,以及所述时频资源与所述第一类型的终端设备的对应关系,确定所述终端设备的类型为第一类型。
  5. 根据权利要求1所述的方法,其特征在于,所述接入设备根据所述第一消息,确定所述终端设备的类型为第一类型,包括:
    所述接入设备根据传输所述第一消息所采用的帧长度、子载波间隔、循环前缀CP长度或者传输时间间隔TTI长度确定所述终端设备的类型为第一类型。
  6. 根据权利要求1所述的方法,其特征在于,所述第一消息为无线资源控制RRC连接请求消息,所述RRC连接请求消息中包含第二指示信息,所述第二指示信息用于指示所述终端设备的类型。
  7. 根据权利要求1所述的方法,其特征在于,所述第一消息为RRC连接建立完成消息,所述RRC连接建立完成消息中包含第三指示信息,所述第三指示信息用于指示所述终端设备的类型为第一类型。
  8. 根据权利要求1所述的方法,其特征在于,所述第一消息为RRC连接建立完成消息,所述RRC连接建立完成消息中包含非接入层NAS消息,所述NAS消息中包含第四指示信息,所述第四指示信息用于指示所述终端设备的类型为第一类型。
  9. 根据权利要求1所述的方法,其特征在于,所述第一消息为RRC连接请求消息或者RRC连接建立完成消息;
    所述接入设备根据所述第一消息,确定所述终端设备的类型为第一类型,包括:
    所述接入设备根据所述RRC连接请求消息或者RRC连接建立完成消息的格式,确定所述终端设备的类型为第一类型。
  10. 根据权利要求1所述的方法,其特征在于,所述第一消息为RRC连接建立完成消息;
    所述接入设备根据所述第一消息,确定所述终端设备的类型为第一类型,包括:
    所述接入设备根据所述RRC连接建立完成消息中的NAS消息的格式,确定所述终端设备的类型为第一类型。
  11. 根据权利要求9或10所述的方法,其特征在于,所述接入设备接收终端设备发送的第一消息之前,还包括:
    所述接入设备向所述终端设备发送能力指示信息,所述能力指示信息用于指示所述接入设备具有接入所述第一核心网的能力。
  12. 一种网络接入方法,其特征在于,包括:
    终端设备生成第一消息;
    所述终端设备向接入设备发送所述第一消息,所述第一消息用于指示终端设备为第一类型的终端设备,其中,所述第一类型的终端设备具备接入第一核心网的能力,所述接入设备连接至少两个不同类型的核心网,所述至少两个不同的核心网包括所述第一核心网。
  13. 根据权利要求12所述的方法,其特征在于,所述终端设备生成第一消息之前,还包括:
    所述终端设备根据待接入的目标核心网,确定所述第一消息的格式。
  14. 根据权利要求12或13所述的方法,其特征在于,所述终端设备向接入设备发送第一消息之前,还包括:
    所述终端设备确定所述接入设备具有接入所述第一核心网的能力。
  15. 根据权利要求14所述的方法,其特征在于,
    所述终端设备确定所述接入设备具有接入第一核心网的能力之前,还包括:
    所述终端设备接收广播消息,所述广播消息中包含能力指示信息,所述能力指示信息用于指示所述接入设备具有接入第一核心网的能力;
    或者,
    所述终端设备接收随机接入响应信息,所述随机接入响应信息中包含所述能力指示信息;
    或者,
    所述终端设备接收无线资源控制RRC连接建立消息,所述RRC连接建立消息中包含所述能力指示信息。
  16. 一种接入设备,其特征在于,包括:
    接收器,用于从终端设备接收第一消息,所述第一消息用于指示所述终端设备为第一类型的终端设备,其中,所述第一类型的终端设备具有接入第一核心网的能力,所述接入设备连接至少两个不同类型的核心网,所述至少两个不同类型的核心网包括所述第一核心网;
    处理器,用于根据所述第一消息,确定所述终端设备的类型为第一类型;
    所述处理器还用于根据所述终端设备的类型,确定所述终端设备接入的目标核心网为所述第一核心网。
  17. 根据权利要求16所述的接入设备,其特征在于,所述第一消息为前导码序列;
    所述处理器具体用于根据所述前导码序列与所述第一类型的终端设备的对应关系,确定所述终端设备的类型为第一类型。
  18. 根据权利要求16所述的接入设备,其特征在于,所述第一消息为前导码序列,所述前导码序列中包含第一指示信息,所述第一指示信息用于指示所述终端设备的类型为第一类型。
  19. 根据权利要求17所述的接入设备,其特征在于,所述处理器具体用于根据所述前导码序列的时频资源,以及所述时频资源与所述第一类型的终端设备的对应关系,确定所述终端设备的类型为第一类型。
  20. 根据权利要求16所述的接入设备,其特征在于,所述处理器具体用于根据传输所述第一消息所采用的帧长度、子载波间隔、循环前缀CP长度或者传输时间间隔TTI长度确定所述终端设备的类型为第一类型。
  21. 根据权利要求16所述的接入设备,其特征在于,所述第一消息为无线资源控制RRC连接请求消息,所述RRC连接请求消息中包含第二指示信息,所述第二指示信息用于指示所述终端设备的类型。
  22. 根据权利要求16所述的接入设备,其特征在于,所述第一消息为RRC连接建立完成消息,所述RRC连接建立完成消息中包含第三指示信息,所述第三指示信息用于指示所述终端设备的类型为第一类型。
  23. 根据权利要求16所述的接入设备,其特征在于,所述第一消息为RRC连接建立完成消息,所述RRC连接建立完成消息中包含非接入层NAS消息,所述NAS消息中包含第四指示信息,所述第四指示信息用于指示所述终端设备的类型为第一类型。
  24. 根据权利要求16所述的接入设备,其特征在于,所述第一消息为RRC连接请求消息或者RRC连接建立完成消息;
    所述处理器具体用于根据所述RRC连接请求消息或者RRC连接建立完成消息的格式,确定所述终端设备的类型为第一类型。
  25. 根据权利要求16所述的接入设备,其特征在于,所述第一消息为RRC连接建立完成消息;
    所述处理器具体用于根据所述RRC连接建立完成消息中的NAS消息的格式,确定所述终端设备的类型为第一类型。
  26. 根据权利要求24或25所述的接入设备,其特征在于,还包括:
    发送器,用于向所述终端设备发送能力指示信息,所述能力指示信息用于指示所述接入设备具有接入所述第一核心网的能力。
  27. 一种终端设备,其特征在于,包括:
    处理器,用于生成第一消息;
    发送器,用于向接入设备发送所述第一消息,所述第一消息用于指示终端设备为第一类型的终端设备,其中,所述第一类型的终端设备具备接入第一核心网的能力,所述接入设备连接至少两个不同类型的核心网,所述至少两个不同的核心网包括所述第一核心网。
  28. 根据权利要求27所述的终端设备,其特征在于,所述处理器还用于根据待接 入的目标核心网,确定所述第一消息的格式。
  29. 根据权利要求27或28所述的终端设备,其特征在于,所述处理器还用于确定所述接入设备具有接入所述第一核心网的能力。
  30. 根据权利要求29所述的终端设备,其特征在于,
    还包括:
    接收器,用于接收广播消息,所述广播消息中包含能力指示信息,所述能力指示信息用于指示所述接入设备具有接入第一核心网的能力;
    或者,
    所述接收器,用于接收随机接入响应信息,所述随机接入响应信息中包含所述能力指示信息;
    或者,
    所述接收器,用于接收无线资源控制RRC连接建立消息,所述RRC连接建立消息中包含所述能力指示信息。
PCT/CN2017/098038 2016-08-22 2017-08-18 网络接入方法、接入设备和终端设备 WO2018036421A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17842844.7A EP3477999B1 (en) 2016-08-22 2017-08-18 Network access method, access device and terminal device
US16/281,815 US10834775B2 (en) 2016-08-22 2019-02-21 Network access method, access device, and terminal device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610702579.5 2016-08-22
CN201610702579.5A CN107770847B (zh) 2016-08-22 2016-08-22 网络接入方法、接入设备和终端设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/281,815 Continuation US10834775B2 (en) 2016-08-22 2019-02-21 Network access method, access device, and terminal device

Publications (1)

Publication Number Publication Date
WO2018036421A1 true WO2018036421A1 (zh) 2018-03-01

Family

ID=61246440

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/098038 WO2018036421A1 (zh) 2016-08-22 2017-08-18 网络接入方法、接入设备和终端设备

Country Status (4)

Country Link
US (1) US10834775B2 (zh)
EP (1) EP3477999B1 (zh)
CN (1) CN107770847B (zh)
WO (1) WO2018036421A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20190108252A (ko) * 2018-03-14 2019-09-24 삼성전자주식회사 무선 베어러를 설정하는 방법 및 장치
CN110557827B (zh) * 2018-05-30 2022-10-28 展讯通信(上海)有限公司 一种双网络的注册方法及基站
MX2021011545A (es) * 2019-03-29 2021-10-22 Ericsson Telefon Ab L M Ue, nodos de red para el manejo de información de categoría de ue.

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1761353A (zh) * 2004-10-11 2006-04-19 华为技术有限公司 终端接入不同核心网的方法
CN101459937A (zh) * 2008-12-31 2009-06-17 华为技术有限公司 核心网节点的接入方法和***及接入设备
US20150127843A1 (en) * 2008-11-25 2015-05-07 Broadcom Corporation Multiple Pathway Session Setup to Support QOS Services

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7305251B2 (en) * 2003-10-07 2007-12-04 Motorola Inc. Method for selecting a core network
US20060246899A1 (en) * 2005-04-28 2006-11-02 Research In Motion Limited System and method for providing network advertisement information via a network advertisement broker (NAB)
US8428584B2 (en) * 2005-07-01 2013-04-23 Research In Motion Limited System and method for accelerating network selection by a wireless user equipment (UE) device
US20070004402A1 (en) * 2005-07-01 2007-01-04 Research In Motion Limited System and method for managing network lists in a wireless user equipment (UE) device
US8010105B2 (en) * 2006-05-19 2011-08-30 Research In Motion Limited System and method for facilitating accelerated network selection using a weighted network list
KR20100013270A (ko) * 2008-07-30 2010-02-09 삼성전자주식회사 코어 네트워크 정보를 관리하기 위한 방법 및 시스템
CN102123477B (zh) * 2010-01-08 2015-06-10 中兴通讯股份有限公司 M2m核心网络的接入实现方法及装置
EP2421305A1 (en) * 2010-08-20 2012-02-22 Vodafone Holding GmbH Routing of a message in a shared radio access network
GB2492544A (en) * 2011-07-01 2013-01-09 Intellectual Ventures Holding 81 Llc Selecting a radio access type for packet data communication
CN103765974B (zh) * 2011-08-19 2017-12-08 交互数字专利控股公司 在移动站中使用非接入层过程来访问属于不同无线电接入技术的分量载波的方法和设备
CN102984782B (zh) * 2011-09-02 2018-04-20 中兴通讯股份有限公司 一种多模智能接入方法、设备和***
CN102413546A (zh) * 2011-12-01 2012-04-11 大唐移动通信设备有限公司 一种核心网设备的选择方法和设备
US20130182680A1 (en) * 2012-01-18 2013-07-18 Electronics And Telecommunications Research Institute Method for machine type communication user equipment to connect to evolved node-b and apparatus employing the same
TW201807961A (zh) * 2012-09-27 2018-03-01 內數位專利控股公司 在噓擬網路中端對端架構、api框架、發現及存取
WO2015000134A1 (en) * 2013-07-02 2015-01-08 Telefonaktiebolaget L M Ericsson(Publ) Method and network node for managing collisions
JP6420337B2 (ja) * 2013-11-01 2018-11-07 華為技術有限公司Huawei Technologies Co.,Ltd. ネットワーク選択方法およびコアネットワーク装置
JP6630675B2 (ja) * 2014-10-06 2020-01-15 シャープ株式会社 Ue、基地局装置、ueの通信制御方法及び基地局の通信制御方法
CN113115412A (zh) * 2015-10-09 2021-07-13 日本电气株式会社 专用核心网(dcn)选择
US10536946B2 (en) * 2015-12-08 2020-01-14 Huawei Technologies Co., Ltd. Method and system for performing network slicing in a radio access network
WO2017124286A1 (zh) * 2016-01-18 2017-07-27 华为技术有限公司 一种plmn的dcn处理方法、ue及dcn服务节点
US10820241B2 (en) * 2016-02-15 2020-10-27 Telefonaktiebolaget Lm Ericsson (Publ) Network nodes and methods performed therein for enabling communication in a communication network
US10257078B2 (en) * 2016-04-01 2019-04-09 Qualcomm Incorporated Interworking with legacy radio access technologies for connectivity to next generation core network
WO2017166314A1 (zh) * 2016-04-01 2017-10-05 华为技术有限公司 一种接入方法、装置、设备及***
EP3843289B1 (en) * 2016-05-11 2022-09-28 Sony Group Corporation Distributed control in wireless systems
CN112040516B (zh) * 2016-08-12 2021-11-26 华为技术有限公司 切换方法、基站及通信***
CN113225784B (zh) * 2016-09-30 2022-08-09 华为技术有限公司 消息的识别方法和装置
CN108024314B (zh) * 2016-11-03 2021-07-16 华为技术有限公司 一种选择网络的方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1761353A (zh) * 2004-10-11 2006-04-19 华为技术有限公司 终端接入不同核心网的方法
US20150127843A1 (en) * 2008-11-25 2015-05-07 Broadcom Corporation Multiple Pathway Session Setup to Support QOS Services
CN101459937A (zh) * 2008-12-31 2009-06-17 华为技术有限公司 核心网节点的接入方法和***及接入设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3477999A4 *

Also Published As

Publication number Publication date
US20190182882A1 (en) 2019-06-13
EP3477999A1 (en) 2019-05-01
EP3477999B1 (en) 2020-08-05
US10834775B2 (en) 2020-11-10
CN107770847A (zh) 2018-03-06
CN107770847B (zh) 2020-11-27
EP3477999A4 (en) 2019-08-14

Similar Documents

Publication Publication Date Title
TWI737844B (zh) 傳輸參考信號的方法和通訊設備
KR20190125959A (ko) Message 3 프로토콜 데이터 유닛을 송수신하는 장치 및 방법
WO2018228433A1 (zh) 一种公共下行控制信道的传输方法和相关设备
US20160352469A1 (en) Communication methods performed by secondary base station and master base station and associated base stations
WO2020135850A1 (zh) 通信方法和装置
WO2018202178A1 (zh) 波束恢复方法及装置
KR102272581B1 (ko) Ta 획득 방법 및 장치
US20230388753A1 (en) Methods for power efficient broadcasting in wlan
US20230086209A1 (en) Method and apparatus for management of extended mobile device identity information
WO2018171626A1 (zh) 随机接入响应的方法和设备以及随机接入的方法和设备
KR20160021439A (ko) 무선 통신 방법, 장치, 및 시스템
CN113038590B (zh) 时间同步方法、电子设备及存储介质
WO2013159596A1 (zh) 一种用户设备到用户设备的通信方法及用户设备
US10834775B2 (en) Network access method, access device, and terminal device
WO2020150706A1 (en) Procedures enabling v2x unicast communication over pc5 interface
WO2015055142A1 (zh) 发现信号的发送和接收方法、以及发送和接收装置
WO2022063173A1 (zh) 传输接收点的确定方法及装置
US10631187B1 (en) Method and apparatus for ranging
WO2019062562A1 (zh) 信息指示方法、用户设备及基站
CN109327914A (zh) 处理双连接的装置及方法
WO2015168908A1 (zh) 资源调度方法、装置及***
WO2014139351A1 (zh) 一种d2d发现信号的传输方法和设备
CN109906646A (zh) 信息传输方法、基站和终端设备
WO2019114670A1 (zh) 一种中继***接入方法及装置
WO2020029837A1 (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: 17842844

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2017842844

Country of ref document: EP

Effective date: 20190122

NENP Non-entry into the national phase

Ref country code: DE