WO2019214683A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2019214683A1
WO2019214683A1 PCT/CN2019/086208 CN2019086208W WO2019214683A1 WO 2019214683 A1 WO2019214683 A1 WO 2019214683A1 CN 2019086208 W CN2019086208 W CN 2019086208W WO 2019214683 A1 WO2019214683 A1 WO 2019214683A1
Authority
WO
WIPO (PCT)
Prior art keywords
cause value
terminal
protocol layer
rrc connection
access
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2019/086208
Other languages
English (en)
French (fr)
Inventor
王瑞
曾清海
梁津垚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to JP2020563718A priority Critical patent/JP7127153B2/ja
Priority to EP19799203.5A priority patent/EP3793263B1/en
Priority to KR1020207034850A priority patent/KR102435491B1/ko
Publication of WO2019214683A1 publication Critical patent/WO2019214683A1/zh
Priority to US17/094,266 priority patent/US11425764B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points

Definitions

  • the present application relates to communication technologies, and in particular, to a communication method and apparatus.
  • future wireless network systems may include multiple wireless access technologies, such as second generation (2rd Generation, 2G) wireless communication technology, third generation (3rd Generation, 3G) wireless communication technology, One or more of 4rd Generation (4G) wireless communication technology, 5rd Generation (5G) wireless communication technology, and further advanced wireless access technology.
  • future wireless network systems may also include wireless access technologies defined by non-3GPP organizations, such as wireless local area networks (WLANs), Bluetooth, short-range communication technologies, and the like.
  • WLANs wireless local area networks
  • Bluetooth short-range communication technologies
  • a radio access network device supporting one or more radio access technologies may be connected to a plurality of core networks using different technologies, and the core network type may be a 2G core network, a 3G core network, or a 4G core network (The Evolved Packet) Core, EPC), 5G core network (5G Core, 5GC), and core network types for further evolution in the future.
  • EPC The Evolved Packet
  • 5G Core 5GC
  • core network types for further evolution in the future.
  • the types of services become more and more abundant, the capabilities of the terminal and the radio access network device become stronger and stronger. Therefore, when the terminal establishes a connection with the radio access network device, it is desirable that the terminal can provide more connection establishment cause values. Used for wireless access networks for processing and network optimization.
  • the cause value corresponding to the wireless communication system to which the multiple core networks belong needs to be carried in the same wireless access technology.
  • the defined message format In the defined message format.
  • the present application provides a communication method and apparatus, so that when a terminal accesses different core networks through a radio access technology, the cause value can be reported normally.
  • a first aspect of the present application provides a communication method, the method comprising:
  • the terminal first determines the first radio access technology used to establish the RRC connection, and the terminal determines, according to the access information, the first cause value of establishing the RRC connection, where the first cause value is the reason of the first radio access technology.
  • the access information includes at least one of an access identifier AI, an access category AC, and a second cause value of the second radio access technology.
  • the terminal may determine a first cause value according to an access message including at least one of an AI, an AC, and a second cause value, where the first cause value is a cause value of the first radio access technology, and the second The cause value is the cause value of the second radio access technology. Therefore, when the wireless access device provides a plurality of services of the core network using different technologies to the terminal through a wireless access technology, the cause value of the communication with the different core network sent by the terminal to the wireless access device may be carried in the same The message format defined by the radio access technology. Therefore, when the terminal accesses a plurality of core networks by using one type of wireless access technology, the reason value can be reported normally.
  • the terminal when the terminal accesses the EPC through the ng-eNB, the first cause value of the E-UTRA is used.
  • the terminal accesses the 5GC through the ng-eNB, the corresponding first radio access technology is E-UTRA, and the second wireless If the access technology is NR, the terminal may determine the E-UTRA cause value according to at least one of the cause values of the AI, the AC, and the NR, that is, when the terminal accesses the 5GC, the terminal may also report the message to the ng-eNB by using the E-UTRA.
  • the cause value is used to ensure that the terminal can report the cause value normally when the terminal connects to the EPC and the 5GC through the ng-eNB.
  • the terminal may determine the first cause value according to the mapping relationship between the second cause value and the first cause value.
  • the terminal may determine the first cause value according to the mapping relationship between the AI and the first cause value.
  • the terminal may determine the first cause value according to a mapping relationship between the AC and the first cause value.
  • the first cause value may be determined by the first protocol layer of the terminal according to the access information.
  • the first cause value may be obtained by the second protocol layer of the terminal from the first protocol layer of the terminal, and the first message including the first cause value may be sent by the second protocol layer.
  • the access information may be obtained by the second protocol layer of the terminal from the first protocol layer of the terminal, and the first protocol value is determined by the second protocol layer of the terminal according to the access information.
  • the first radio access technology includes a global terrestrial radio access E-UTRA technology
  • the second radio access technology includes a new air interface NR technology.
  • the first protocol layer is a non-access stratum NAS
  • the second protocol layer is an RRC layer.
  • the establishment of the RRC connection includes establishing a new RRC connection, restoring an RRC connection, or reestablishing an RRC connection.
  • mapping relationship between the second cause value and the first cause value may be configured in advance by any one of the following methods:
  • NAS signaling message configuration operation management, maintenance OAM configuration, carrier pre-configuration, default configuration.
  • mapping relationship between the foregoing AI and the first cause value may be configured in advance by any of the following methods:
  • NAS signaling message configuration operation management, maintenance OAM configuration, carrier pre-configuration, default configuration.
  • mapping relationship between the AC and the first cause value may be configured in any of the following manners:
  • NAS signaling message configuration operation management, maintenance OAM configuration, carrier pre-configuration, default configuration.
  • a second aspect of the present application provides a communication device comprising a processor for coupling with a memory to read and execute instructions in the memory to implement the method of the first aspect above.
  • the communication device may further include a transceiver, configured to support the communication device to perform data transmission, signaling, or information in the foregoing method of the first aspect, for example, sending the first message.
  • the communication device may be a terminal device or a part of the terminal device, such as a chip system in the terminal device.
  • the chip system is configured to support the terminal device to implement the functions involved in the foregoing aspects, for example, generating, receiving, transmitting, or processing data and/or information involved in the foregoing method.
  • the chip system further comprises a memory for storing necessary program instructions and data of the terminal device.
  • the chip system, including the chip may also include other discrete devices or circuit structures.
  • a third aspect of the present application provides a communication device having the functions of implementing the first aspect. These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the electronic device may include a processing module and a sending module, and the processing module and the sending module may perform corresponding functions in the foregoing methods, for example, a processing module, configured to determine a first wireless used to establish an RRC connection.
  • a processing module configured to determine a first wireless used to establish an RRC connection.
  • An access technology and determining, according to the access information, a first cause value for establishing the RRC connection, where the access information includes at least one of an AI, an AC, and a second cause value of the second radio access technology; And sending the first message, where the first message is used to request to establish the RRC connection, where the first message includes the first cause value.
  • a fourth aspect of the present application provides a readable storage medium storing a computer program, the computer program comprising instructions for performing the method of the first aspect described above.
  • a fifth aspect of the present application provides a computer program product comprising computer program code for causing a computer to perform the method of the first aspect when the computer program code is executed.
  • the foregoing computer program code may be stored in whole or in part on the first storage medium, where the first storage medium may be packaged with the processor or may be separately packaged with the processor. Specifically limited.
  • 1 is a system architecture diagram of a 5G wireless communication system
  • FIG. 2 is a schematic diagram of a connection where an ng-eNB is simultaneously connected to a 5GC and an EPC;
  • 3 is a protocol stack of a terminal supporting two radio access technologies and an architecture diagram connected to the ng-eNB;
  • FIG. 4 is a schematic flowchart diagram of Embodiment 1 of a communication method provided by the present application.
  • FIG. 5 is a first interaction flowchart of a communication method provided by the present application.
  • FIG. 6 is a second interaction flowchart of a communication method provided by the present application.
  • FIG. 7 is a third interaction flowchart of a communication method provided by the present application.
  • FIG. 8 is a physical block diagram of a communication device provided by the present application.
  • FIG. 9 is a block diagram of a communication device provided by the present application.
  • At least one of the embodiments described in the embodiments of the present application means “one” or “one or more.”
  • Illustrative, including at least one of A, B, and C, may mean the following:
  • the 4G wireless communication system is based on Evolved-UMTS Terrestrial Radio Access (E-UTRA) technology
  • the 5G wireless communication system (5G System, 5GS) is based on the new air interface (New Radio). , NR) technology for communication.
  • E-UTRA Evolved-UMTS Terrestrial Radio Access
  • 5G System 5GS
  • NR new air interface
  • the terminal When the terminal is connected to the radio access network device, it can be connected using one or more radio access technologies.
  • different terminals can access the 5G core network by using NR and E-UTRA respectively. Therefore, the NAS layers used by different terminals are 5GS NAS, and the used RRC layer is the corresponding NR RRC or E-UTRA RRC.
  • FIG. 1 is a system architecture diagram of a 5G wireless communication system, as shown in FIG. 1 , mainly composed of 5GC and 5G RAN (also referred to as NG-RAN), wherein 5GC is a core network of 5GS, which may include access and mobile Network elements such as Access and Mobility Management Function (AMF) and User Plane Function (UPF).
  • the 5G RAN is a radio access network of a 5G wireless communication system.
  • gNB provides the terminal with the NR user plane and the control plane protocol stack endpoint.
  • the ng-eNB provides the terminal of the evolved E-UTRA user plane and control plane protocol stack for the terminal.
  • the ng-eNB For the ng-eNB, it can be connected to the 5GC to enable the terminal to access the 5GC through the ng-eNB. At the same time, it can also be connected to the EPC of the 4G, so that the terminal accesses the EPC through the ng-eNB.
  • the ng-eNB E-UTRA technology When the ng-eNB is connected to the 5GC, the ng-eNB E-UTRA technology provides the terminal with wireless transmission resources and provides the 5GC service for the terminal.
  • the ng-eNB may be connected only to the 5GC or the EPC, or the ng-eNB may connect to the 5GC and the EPC at the same time.
  • 2 is a schematic diagram of a connection where an ng-eNB is simultaneously connected to a 5GC and an EPC. As shown in FIG. 2, the ng-eNB is simultaneously connected to the 5GC and the EPC.
  • the terminal can access the EPC through the legacy eNB and access the 5GC through the gNB.
  • the ng-eNB and the gNB are both connected to the 5GC, and the terminal can access the 5GC through the ng-eNB or the gNB.
  • the ng-eNB and the gNB can be connected to each other for communication between the base stations and to exchange information related to the terminal. Meanwhile, when there is a legacy eNB in the network, the ng-eNB is connected to the eNB, used for communication between the base stations, and interacts with the terminal-related information.
  • a conventional LTE terminal can access an EPC through an eNB or an ng-eNB.
  • the 5GC can be accessed through the gNB or the 5GC can be accessed through the ng-eNB.
  • the ng-eNB it can be connected to the 5GC or to the EPC.
  • FIG. 3 is a schematic diagram of a protocol stack of a terminal supporting two radio access technologies and a connection with an ng-eNB.
  • the terminal supports both NR technology and E-UTRA technology, that is, access to 5GC. , you can also access the EPC. Assume that the terminal supports access to the 5GC through the gNB and the ng-eNB.
  • the terminal supports the air interface protocol stack of the NR, for example, including the NR RRC protocol layer and the NR underlying protocol layer (such as the RLC, MAC, and PHY layers). ), and the Non-Access Stratum (NAS) defined for 5GS, referred to as the 5GS NAS protocol layer.
  • NAS Non-Access Stratum
  • the terminal also supports the air interface protocol stack of E-UTRA, including, for example, E-UTRA RRC, E-UTRA underlying protocol layer, and 5GS NAS protocol layer.
  • E-UTRA RRC E-UTRA RRC
  • E-UTRA underlying protocol layer E-UTRA underlying protocol layer
  • 5GS NAS protocol layer E-UTRA protocol layer
  • the terminal also needs to support the NAS protocol layer defined for the EPS, which is referred to as an EPS NAS. If the terminal supports an access mode, the corresponding protocol stack needs to be supported inside the terminal.
  • EPS NAS NAS protocol layer defined for the EPS
  • FIG. 3 only supports two terminals of the radio access technology as an example, but the embodiment of the present application is also applicable to a terminal that supports one radio access technology.
  • the technical solution of the embodiment of the present application can also be applied.
  • the technical solution of the embodiment of the present application can also be applied.
  • the technical solution of the present application is mainly for the scenario that the terminal accesses the 5GC through the ng-eNB.
  • the following embodiments of the present application may also The process of the terminal passing through the gNB is described.
  • the existing terminal Before the existing terminal sends signaling or data to the core network (for example, 5GC or EPC), it needs to first send an RRC request to the base station (for example, gNB or ng-eNB) to establish an RRC connection.
  • the base station for example, gNB or ng-eNB
  • the terminal carries the cause value in the RRC request, which is used to identify the reason for the current access of the terminal.
  • the above RRC request may be used to request a new RRC connection or to resume an RRC connection.
  • the recovering the RRC connection may restore the suspended RRC connection to an RRC connection capable of normal communication when the UE transitions from the third state (or referred to as an inactive state) to the connected state.
  • the specific RRC message may be an RRC Connection Request, ie, an RRC Setup Request, an RRC Setup Request, an RRC Resume Request, or an RRC Connection Resume Request. Wait.
  • the cause value in the RRC request specified by the LTE-related protocol occupies 3 bits in total, and can carry up to 8 types of values.
  • the current protocol specifies seven kinds of cause values (not excluded in the future evolution of the LTE system, More than 7 cause values will be defined, for example, 8), namely: emergency service (ie, emergency), high priority access (ie highPriorityAccess), terminal terminating access (mt-Access), terminal Mobile originating signalling (mo-Signalling), mobile originating data (mo-data), delay-tolerant access (ie, delayTolerantAccess), mobile originating voice call (mobile originating voice call, mo-VoiceCall).
  • emergency service ie, emergency
  • highPriorityAccess high priority access
  • mt-Access terminal terminating access
  • mo-Signalling terminal Mobile originating signalling
  • mobile originating data mi-data
  • delay-tolerant access ie, delayTolerantAccess
  • mobile originating voice call mobile originating voice call, mo-VoiceCall
  • the number of cause values that the terminal can carry in the RRC request may be more than the number specified in the EPS system, for example, 8 or more than 8. If the number of cause values specified in the 5GS is large, more fields need to be occupied in the RRC request to carry the cause value.
  • the cause value in the RRC request sent by the terminal when accessing the 5GC is generated by the 5GS NAS, and then carried in the RRC message and then sent by the lower layer protocol stack. If the terminal accesses the 5GC through the gNB, the terminal sends an RRC request to the gNB.
  • the gNB provides wireless transmission resources for the terminal through the NR technology, the NR is used as a new air interface, and a new RRC message format can be defined. Therefore, more fields than the EPS can be directly used to carry the reason. value.
  • the terminal accesses the 5GC through the ng-eNB, the terminal needs to send an RRC request to the ng-eNB.
  • the ng-eNB provides radio transmission resources for the terminal through the E-UTRA technology. Therefore, the length of the field occupied by the cause value in the RRC request needs to comply with the E-UTRA protocol, that is, the number of cause values is 7. (up to 8). In this case, if the terminal does not process the cause value before sending the RRC request to the ng-eNB, the cause value transmission is abnormal.
  • the technical solution described in the present application aims to solve the above problems.
  • the terminal described in the following embodiments of the present application is any terminal that can access the 5GC through the ng-eNB.
  • the terminal may include, but is not limited to, a terminal device applied in the Internet of Things, for example, may be a terminal device (which may be referred to as an “NB-IoT terminal”) in the NB-IoT: Intelligent meter reading equipment, logistics tracking equipment, environmental monitoring equipment, etc.; the terminal may also include but is not limited to a mobile station (Mobile Station, MS), a mobile terminal (Mobile Terminal), a mobile telephone (Mobile Telephone), and a user equipment (User Equipment) (UE), mobile phone (handset) and portable equipment (portable equipment), etc.
  • the terminal device can communicate with one or more core networks via a Radio Access Network (RAN), for example, the terminal device can be mobile A telephone (or "cellular" telephone), a computer with wireless communication capabilities, etc., the terminal device can also be a portable, pocket, handheld, computer built-
  • RAN Radio Access Network
  • FIG. 4 is a schematic flowchart of Embodiment 1 of a communication method provided by the present application. As shown in FIG. 4, the method includes:
  • the terminal determines to establish a first radio access technology used by the RRC connection.
  • the first protocol layer of the terminal may obtain, from the second protocol layer, the first radio access technology used to establish an RRC connection.
  • the first protocol layer may be a NAS
  • the second protocol layer may be an RRC layer.
  • the foregoing first protocol layer may be a 5GS NAS as illustrated in FIG. 3, and the second protocol layer may be an E-UTRA RRC as illustrated in FIG.
  • first protocol layer As a 5GS NAS and the second protocol layer as an E-UTRA RRC as an example.
  • present application is not limited thereto, and the foregoing first protocol layer and the second protocol layer may also be protocol layers of other wireless communication systems or access technologies.
  • the foregoing first radio access technology may be E-UTRA.
  • the terminal determines, according to the access information, a first cause value of the foregoing RRC connection, where the first cause value is a cause value of the first radio access technology, where the access information includes an access identifier (Access Identity, AI), At least one of an access category (AC) and a second cause value of the second radio access technology.
  • access Identity AI
  • AC access category
  • the access information includes at least one of an AI, an AC, and a second cause value of the second radio access technology, and specifically includes the following situations:
  • Access information includes AI
  • the access information includes the second cause value
  • Access information includes AI and AC
  • Access information includes AI and second cause value
  • Access information includes AC and second cause value
  • Access information includes AI, AC, and second cause value
  • the foregoing AI and AC acquisition processes may be as follows:
  • the 5GS NAS detects in real time whether an access attempt triggered by one of the following events occurs:
  • A, 5GMM receives a voice call initiation indication (ie, MO-MMTEL-voice-call-started indication), a video call initiation indication (or MO-MMTEL-video-call-started indication) or an SMS over IP start indication (ie, MO-SMSoIP-attempt-started indication)
  • a voice call initiation indication ie, MO-MMTEL-voice-call-started indication
  • a video call initiation indication or MO-MMTEL-video-call-started indication
  • an SMS over IP start indication ie, MO-SMSoIP-attempt-started indication
  • the 5GMM receives the request of the SMS over NAS initiated by the terminal from the upper layer (except that the service request process triggered by the request needs to convert the UE from the 5GMM idle state to the 5GMM connected state).
  • the 5GMM receives the UL NAS TRANSPORT message from the upper layer for establishing a protocol data unit (PDU) session (except when the service request flow triggered by the request needs to convert the UE from the 5GMM idle state to the 5GMM connection state)
  • PDU protocol data unit
  • the 5GMM receives the UL NAS TRANSPORT message from the upper layer for the modification of the PDU session (except that the service request procedure triggered by the request needs to convert the UE from the 5GMM idle state to the 5GMM connected state)
  • the 5GMM receives a request from the upper layer for reestablishing the user plane resource of the existing PDU session.
  • At least one AI and one AC are obtained according to a preset mapping relationship.
  • the preset mapping relationship may specifically be a mapping relationship specified in the protocol.
  • the AI can be distinguished by an AI identifier or an index value.
  • AI0 and AI1 respectively identify an AI of a specific meaning.
  • the AC can also be distinguished by an AC identifier or an index value.
  • AC0 and AC1 respectively identify an AC of a specific meaning.
  • the 5GS NAS is mapped to AI1
  • the terminal is configured with a Multimedia Priority Service (MPS) terminal
  • the 5GS NAS is mapped to AI1.
  • MCS Mission Critical Service
  • the 5GS NAS is mapped to AI2.
  • the 5GS NAS is mapped to AC0, and if the type of access attempt is an emergency call, the 5GS NAS is mapped to AC2.
  • the obtaining process of the second reason value is:
  • the 5GS NAS determines the second cause value according to at least one of AI, AC, and type of access attempt.
  • the access attempt type is used to identify a call type.
  • the type of access attempt may be an emergency call, a response to a page, or a video call initiated by a terminal.
  • the second cause value is a value of the establishment of the second radio access technology.
  • the second radio access technology may be an NR.
  • the 5GS NAS obtains the second cause value based on Table 1 below.
  • the value of AI includes AI0, AI1, ..., AIX
  • the value of AC includes AC0, AC1, ..., ACY
  • the second cause value (that is, the RRC establishment cause value in the table) contains N different values.
  • X is an integer greater than
  • Y is an integer greater than
  • N is an integer greater than zero.
  • the terminal may determine the first cause value according to at least one of the three.
  • the terminal can determine the first cause value in the following three ways:
  • the terminal determines the first cause value according to the mapping relationship between the second reason value and the first cause value.
  • mapping relationship between the second cause value and the first cause value may be a representation defined in Table 2 below.
  • the first cause value has M different values, where M is an integer greater than 0, and M is less than N.
  • Second cause value First cause value The first value of the second cause value One of the M first cause values Second value of the second cause value One of the M first cause values ... One of the M first cause values The Nth value of the second cause value One of the M first cause values
  • the value of all the first cause values is the same as the value of the second cause value, and the second cause value includes the NM first cause values.
  • the second table may include only the mapping relationship between the value of the second cause value and the value of the first cause value which are not included in the N-M first cause values.
  • the kth value of the second cause value (where k is greater than or equal to 1, less than or equal to N) is a cause value for indicating a video service, and the first cause value does not include the value, and the second table may indicate that the value is
  • the value of the kth value of the second cause value is mapped to the L value of the first cause value (for example, the cause value indicating the voice service, which may be a voice call cause value initiated by the terminal), as shown in Table 2-1 below.
  • Second reason value (total N-M) First cause value The kth value of the second cause value One of the M first cause values (example)
  • the terminal determines the first cause value according to the mapping relationship between the AI and the first cause value.
  • the terminal determines the first cause value according to the mapping relationship between the AC and the first cause value.
  • the terminal determines the first cause value according to the mapping relationship between the second cause value and the first cause value, and the mapping relationship between the second cause value and the first cause value may be performed by any one of the following methods. set up:
  • the core network sends the foregoing mapping relationship to the terminal through the NAS signaling message, and the operation management and maintenance (OAM) configuration sends the above mapping relationship to the terminal, the operator pre-configuration, and the default configuration.
  • OAM operation management and maintenance
  • the foregoing operator pre-configuration may be, for example, that the operator writes the configuration information to the device of the terminal in advance, or the operator writes the configuration information into the Universal Subscriber Identity Module (USIM) in advance. After the USIM card is inserted into the terminal, the terminal acquires configuration information.
  • USIM Universal Subscriber Identity Module
  • the default configuration may be, for example, a configuration specified by the protocol.
  • the mapping between the second cause value and the first cause value may be specified in the protocol of the 5GS NAS or the E-UTRA RRC protocol.
  • mapping relationship between the AI and the first cause value, and the mapping relationship between the AC and the first cause value may also be established by any of the above methods, and will not be described again.
  • the terminal may further determine the first cause value according to the access attempt type.
  • the terminal may determine the first cause value according to the mapping relationship between the AI and the first cause value and the mapping relationship between the AC and the first cause value.
  • a possible implementation manner is terminal acquisition.
  • a mapping relationship that is, a mapping relationship between the AI and the AC and the first cause value, thereby determining the first cause value.
  • the mapping relationship between the AI and the AC and the first cause value may be defined in a manner similar to that in Table 1, as shown in Table 3 below.
  • the value of all the first cause values is the same as the value of the second cause value, and the second cause value includes the NM first cause values.
  • part of the mapping relationship in Table 3 is exactly the same as the mapping relationship of the table, and Table 3 may also contain only the parts different from those in Table 1, as shown in Table 3-1 below.
  • the obtained second cause value is one of the first cause values, and the mapping relationship between the AI and the AC and the value of the first cause value is not required to be carried in Table 3-1.
  • the terminal includes a first protocol layer and a second protocol layer, where the first protocol layer may be, for example, a NAS, and the second protocol layer may be, for example, an RRC layer.
  • the terminal accesses the 5GC through the gNB as an example.
  • the NR cause value is generated by the 5GS NAS of the terminal.
  • the 5GS NAS sends the NR cause value to the NR RRC, and is further sent to the gNB by the NR RRC.
  • the terminal can be executed in the following two alternative ways:
  • the first protocol layer may determine the first cause value by using any one of the foregoing mapping manners or a combination thereof.
  • the first protocol layer is a 5GS NAS
  • the terminal determines the first cause value according to the mapping relationship between the AI and the AC and the first cause value. Then the specific implementation process of this method is:
  • the 5GS NAS first acquires the AI and the AC. Further, the 5GS NAS obtains the first cause value based on the mapping relationship between the AI and the AC and the first cause value.
  • the 5GS NAS sends the first cause value to the E-UTRA RRC, and directly sends the E-UTRA RRC to the ng-eNB. That is, the first protocol value is obtained from the first protocol layer by the second protocol layer, and the first message including the first cause value is transmitted.
  • the second protocol layer first obtains the access information from the first protocol layer, and further determines the first cause value according to the access information.
  • the first protocol layer sends at least one of an AI, an AC, and a second cause value of the second access technology to the second protocol layer.
  • the first protocol layer may also send the second protocol layer to the second protocol layer.
  • the second protocol layer may determine the first cause value by using any one of the above mapping methods or a combination thereof.
  • the first protocol layer is a 5GS NAS
  • the terminal determines the first cause value according to the mapping relationship between the AI and the AC and the first cause value. Then the specific implementation process of this method is:
  • the 5GS NAS first acquires the AI and AC, and then the 5GS NAS sends the AI and AC to the E-UTRA RRC. After receiving the AI and the AC, the E-UTRA RRC obtains the first cause value based on the mapping relationship between the AI and the AC and the first cause value.
  • the method may be sent as follows:
  • the first protocol layer determines a second cause value corresponding to the second radio access technology, and the first protocol layer sends the second cause value to the second protocol layer of the first radio access technology.
  • the first protocol layer determines that the radio access technology (RAT) used by the terminal is the first radio access technology, the first protocol layer directly sends the AI and the AC to the second protocol layer.
  • RAT radio access technology
  • the first protocol layer determines a second cause value corresponding to the second radio access technology.
  • the first protocol layer directly sends the AI and the AC to the second protocol layer. If the second cause value determined by the first protocol layer belongs to a value of the first cause value of the first radio access technology, the first protocol layer directly sends the second cause value to the second protocol layer. As the first cause value of the first radio access technology.
  • the first protocol layer generates a second cause value, and when the value of the first cause value includes the second cause value, the first protocol layer sends the second cause value as the first cause value to the second a protocol layer, where the second protocol layer is carried in the first message; when the value of the first cause value does not include the second cause value, the first protocol layer sends the AI and the AC to the second protocol layer, where The first protocol value is obtained based on the AI and the AC at the second protocol layer (for example, according to the mapping relationship shown in Table 3-1).
  • the terminal sends a first message, where the first message is used to request to establish an RRC connection, where the first message includes the first cause value.
  • the first cause value is carried in the first message and sent out.
  • the foregoing first message may be a message for creating a new RRC connection, a message for restoring an RRC connection, or a message for reestablishing an RRC connection.
  • the message of the newly established RRC connection may be an RRC connection request message (RRC Connection Request)
  • the message for restoring the RRC connection may be an RRC Connection Resume Request message
  • the message for reestablishing the RRC connection may be an RRC connection reestablishment request message. (RRC Connection Reestablishment Request).
  • the terminal may determine the first cause value according to the access message including at least one of the AI, the AC, and the second cause value, where the first cause value is a cause value of the first radio access technology, and the second The cause value is the cause value of the second radio access technology. Therefore, when the wireless access device provides a plurality of services of the core network using different technologies to the terminal through a wireless access technology, the cause value of the communication with the different core network sent by the terminal to the wireless access device may be carried in the same The message format defined by the radio access technology. Therefore, when the terminal accesses a plurality of core networks by using one type of wireless access technology, the reason value can be reported normally.
  • the terminal when the terminal accesses the EPC through the ng-eNB, the first cause value of the E-UTRA is used.
  • the terminal accesses the 5GC through the ng-eNB, the corresponding first radio access technology is E-UTRA, and the second wireless If the access technology is NR, the terminal may determine the E-UTRA cause value according to at least one of the cause values of the AI, the AC, and the NR, that is, when the terminal accesses the 5GC, the terminal may also report the message to the ng-eNB by using the E-UTRA.
  • the cause value is used to ensure that the terminal can report the cause value normally when the terminal connects to the EPC and the 5GC through the ng-eNB.
  • the first radio access technology is E-UTRA
  • the second radio access technology is NR
  • the first protocol layer is 5GS NAS
  • the second protocol layer is E-UTRA RRC as an example to illustrate the completeness of the application. Implementation process.
  • FIG. 5 is a first interaction flowchart of the communication method provided by the present application. As shown in FIG. 5, the first cause value is generated by the 5GS NAS and sent to the E-UTRA RRC.
  • the specific execution process is as follows:
  • the 5GS NAS acquires a radio access technology of the RRC layer.
  • the terminal has performed cell selection or cell reselection and resides in one cell.
  • the radio access technology of the RRC layer refers to a radio access technology used by a cell camped by the terminal.
  • the terminal camps in the E-UTRA cell, and the radio access technology of the RRC layer is E-UTRA.
  • the 5GS NAS is already in working state, so the RAN accessed by the terminal is NG-RAN. Since the NG-RAN can provide two radio access technologies, namely NR and E-UTRA, the 5GS NAS knows that the radio access technology corresponding to the RRC layer is NR or E-UTRA. If the function of the 5GS NAS includes providing different parameters (such as a cause value) for the RRC of the NR and the RRC of the E-UTRA, the 5GS NAS needs to acquire whether the radio access technology of the RRC layer is NR or E-UTRA.
  • the 5GS NAS does not need to further acquire whether the radio access technology of the RRC layer is NR or E-UTRA.
  • the 5GS NAS sends a request to the RRC layer to trigger the RRC layer to perform RRC connection establishment.
  • the 5GS NAS determines that the radio access technology of the RRC layer is E-UTRA.
  • the 5GS NAS determines a cause value (second cause value) of the NR according to at least one of an AI, an AC, and an access attempt type.
  • the 5GS NAS can determine the cause value of the NR according to the specific method in the embodiment shown in FIG. 4.
  • the 5GS NAS determines the second cause value according to Table 1.
  • the 5GS NAS determines a cause value (first cause value) of the E-UTRA according to at least one of an AI, an AC, a second cause value, and an access attempt type.
  • the 5GS NAS can determine the cause value of the E-UTRA according to the specific method in the embodiment shown in FIG. 4.
  • the 5GS NAS determines the first cause value according to Table 2, Table 2-1, Table 3, or Table 3-1. It should be noted that S504 is an optional step. For example, if the 5GS NAS determines the first cause value only based on AI and AC, then S504 need not be performed.
  • 5GS NAS sends the cause values of AI, AC, and E-UTRA to the E-UTRA RRC layer.
  • the S507 and the E-UTRA RRC layer read the system information of the resident cell, and obtain the access control parameter therein.
  • the above access control parameters include an access ratio and a forbidden time associated with the AC, and a bitmap (Bitmap) associated with the AI.
  • the E-UTRA RRC layer determines whether the cell is barred according to the AI, the AC, and the foregoing access control parameter. If it is in the disabled state, S509 is executed, and if it is not in the prohibited state, S510 is executed.
  • the E-UTRA RRC layer sends indication information indicating that the NAS layer access is prohibited to the 5GS NAS.
  • the E-UTRA RRC layer sends an RRC message to the ng-eNB.
  • This RRC message is collectively referred to as Message 3 (Message3, MSG3).
  • the cause value of the E-UTRA carried in the MSG3 is used to indicate the reason why the ng-eNB initiates connection establishment or recovery.
  • the ng-eNB receives the MSG3 and obtains a cause value of the E-UTRA.
  • the ng-eNB determines whether the terminal is allowed to access, and replies to message 4 (Message4, MSG4).
  • the MSG 4 carries an RRC message indicating that access is allowed, and may be, for example, RRC Connection Setup, RRC Connection Resume.
  • the RRC message indicating the rejection is carried in the MSG4, and may be, for example, RRC Connection Reject, RRC Connection Resume Reject.
  • the ng-eNB sends the E-UTRA cause value to the 5GC network element (for example, AMF) for assisting the 5GC to perform access control for the terminal.
  • the 5GC network element for example, AMF
  • FIG. 6 is a second interaction flowchart of the communication method provided by the present application. As shown in FIG. 6, the first cause value is generated by the 5GS NAS and sent to the E-UTRA RRC.
  • the specific execution process is as follows:
  • the S601 and 5GS NAS acquire the radio access technology of the RRC layer.
  • the terminal Prior to this step, the terminal has performed cell selection or cell reselection and resides in one cell.
  • the 5GS NAS sends an Access Attempt to the RRC layer to trigger the RRC layer to perform RRC connection establishment, RRC connection reply, or RRC connection reestablishment.
  • 5GS NAS determines that the radio access technology of the RRC layer is E-UTRA.
  • the 5GS NAS determines a cause value (second cause value) of the NR according to at least one of an AI, an AC, and an access attempt type.
  • the 5GS NAS can determine the cause value of the NR according to the specific method in the embodiment shown in FIG. 4.
  • the 5GS NAS determines the second cause value according to Table 1.
  • 5GS NAS sends the cause values of AI, AC, and NR to the E-UTRA RRC layer.
  • S604 is an optional step. For example, if the E-UTRA RRC layer does not need to use the NR cause value to determine the first cause value, then S504 need not be performed, and in this step, the 5GS NAS does not need to send the NR cause value to the E-UTRA RRC layer.
  • the E-UTRA RRC layer reads a system information of a resident cell, and obtains an access control parameter therein.
  • the above access control parameters include an access ratio and a forbidden time associated with the AC, and a bitmap (Bitmap) associated with the AI.
  • the E-UTRA RRC layer determines whether the cell is barred according to the AI, the AC, and the foregoing access control parameter. If it is in the disabled state, S608 is executed, and if it is not in the prohibited state, S609 and S610 are executed.
  • the E-UTRA RRC layer sends indication information indicating that the NAS layer access is prohibited to the 5GS NAS.
  • the E-UTRA RRC layer determines the cause value of the E-UTRA according to at least one of a cause value of the AI, the AC, and the NR, and an access attempt type.
  • the step S609 may occur between step S605 and step S607.
  • the E-UTRA RRC layer may determine the cause value of the E-UTRA according to the specific method in the embodiment shown in FIG. 4.
  • the E-UTRA RRC determines the first cause value according to Table 2, Table 2-1, Table 3, or Table III-1.
  • the E-UTRA RRC layer sends an RRC message to the ng-eNB.
  • This RRC message is collectively referred to as MSG3.
  • the reason value of the E-UTRA carried in the MSG3 is used to indicate the reason why the NG-eNB initiates the establishment or restoration of the RRC connection.
  • the ng-eNB receives the MSG3 and obtains a cause value of the E-UTRA.
  • the ng-eNB determines whether access of the terminal is allowed, and returns the MSG4.
  • the MSG 4 carries an RRC message indicating that access is allowed, and may be, for example, RRC Connection Setup, RRC Connection Resume.
  • the RRC message indicating the rejection is carried in the MSG4, and may be, for example, RRC Connection Reject, RRC Connection Resume Reject.
  • the ng-eNB sends the E-UTRA cause value to the 5GC network element (for example, AMF) for assisting the 5GC to perform access control for the terminal.
  • the 5GC network element for example, AMF
  • the following describes the process in which the terminal accesses the 5GC through the gNB.
  • FIG. 7 is a third interaction flowchart of the communication method provided by the present application. As shown in FIG. 7, the specific process of the terminal accessing the 5GC through the gNB is as follows:
  • the 5GS NAS acquires a radio access technology of the RRC layer.
  • the terminal Prior to this step, the terminal has performed cell selection or cell reselection and resides in one cell.
  • the radio access technology of the RRC layer refers to a radio access technology used by a cell camped by the terminal.
  • the terminal camps in the E-UTRA cell, and the radio access technology of the RRC layer is E-UTRA.
  • the 5GS NAS is already in working state, so the RAN accessed by the terminal is NG-RAN. Since the NG-RAN can provide two radio access technologies, namely NR and E-UTRA, the 5GS NAS knows that the radio access technology corresponding to the RRC layer is NR or E-UTRA. If the function of the 5GS NAS includes providing different parameters (such as a cause value) for the RRC of the NR and the RRC of the E-UTRA, the 5GS NAS needs to acquire whether the radio access technology of the RRC layer is NR or E-UTRA.
  • the 5GS NAS does not need to further acquire whether the radio access technology of the RRC layer is NR or E-UTRA.
  • the 5GS NAS sends a request to the RRC layer to trigger the RRC layer to perform RRC connection establishment, RRC connection reply, or RRC connection reestablishment.
  • the 5GS NAS determines a cause value of the NR according to at least one of an AI, an AC, and an access attempt type. Exemplarily, the 5GS NAS determines the second cause value according to Table 1.
  • the 5GS NAS can determine the cause value of the NR according to the specific method in the embodiment shown in FIG. 4.
  • 5GS NAS sends the cause values of AI, AC, and NR to the NR RRC layer.
  • the NR RRC layer reads a system information of a resident cell, and obtains an access control parameter therein.
  • the above access control parameters include an access ratio and a forbidden time associated with the AC, and a bitmap (Bitmap) associated with the AI.
  • the NR RRC layer determines whether the cell is barred according to the AI, the AC, and the foregoing access control parameter. If it is in the disabled state, S707 is executed, and if it is not in the prohibited state, S708 and S709 are executed.
  • the NR RRC layer sends indication information indicating that the NAS layer access is prohibited to the 5GS NAS.
  • the NR RRC layer sends an RRC message to the gNB.
  • This RRC message is collectively referred to as MSG3.
  • the reason value of the NR carried in the MSG3 is used to indicate the reason why the gNB initiates connection establishment or recovery.
  • the gNB receives the MSG3 and obtains the cause value of the NR therein.
  • the gNB determines whether access of the terminal is allowed, and returns the MSG4.
  • the MSG 4 carries an RRC message indicating that access is allowed, and may be, for example, RRC Connection Setup, RRC Connection Resume.
  • the RRC message indicating the rejection is carried in the MSG4, and may be, for example, RRC Connection Reject, RRC Connection Resume Reject.
  • the gNB sends the NR cause value to the 5GC network element (for example, AMF) for assisting the 5GC to perform access control for the terminal.
  • the 5GC network element for example, AMF
  • the embodiments shown in FIG. 5, FIG. 6, and FIG. 7 above may be implemented separately in combination with the technical solution shown in FIG. 4.
  • the 5GS NAS can use the method shown in FIG. 4 to determine the cause value of the NR and the E-UTRA cause value.
  • the 5GS NAS can use the method shown in FIG. 4 to determine the cause value of the NAS, and the E-UTRA RRC layer can use the method shown in FIG. 4 to determine the cause value of the E-UTRA.
  • different schemes may be combined and implemented.
  • the 5GS NAS may determine the first cause value only according to the AI or AC, or the 5GS NAS may determine the first cause value according to the AI and the AC at the same time.
  • FIG. 8 is a physical block diagram of a communication device provided by the present application.
  • the communication device may be a terminal device or a part of the terminal device, such as a chip system in the terminal device.
  • the chip system is configured to support the terminal device to implement the functions involved in the foregoing method embodiments, for example, generating, receiving, transmitting, or processing data and/or information involved in the foregoing method.
  • the chip system further includes a memory for storing necessary program instructions and data of the terminal device.
  • the chip system, including the chip may also include other discrete devices or circuit structures.
  • the communication device includes:
  • the processor 801 is configured to be coupled to the memory 802 to read and execute instructions in the memory 802 to implement:
  • processor 801 is further configured to:
  • processor 801 is further configured to:
  • the first cause value is determined according to the mapping relationship between the AI and the first cause value.
  • processor 801 is further configured to:
  • the first cause value is determined according to the mapping relationship between the AC and the first cause value.
  • processor 801 is further configured to:
  • the first cause value is determined by the first protocol layer according to the access information.
  • processor 801 is further configured to:
  • the first cause value is obtained by the second protocol layer from the first protocol layer.
  • the first message including the first cause value described above is transmitted by the second protocol layer.
  • processor 801 is further configured to:
  • the access information is obtained by the second protocol layer from the first protocol layer.
  • the first cause value is determined by the second protocol layer according to the access information.
  • the foregoing first radio access technology includes an E-UTRA technology
  • the second radio access technology includes an NR technology.
  • the first protocol layer is a NAS
  • the second protocol layer is an RRC layer.
  • FIG. 9 is a block diagram of a communication device provided by the present application. As shown in FIG. 9, the device includes:
  • the processing module 901 is configured to determine a first radio access technology used to establish an RRC connection.
  • the sending module 902 is configured to send a first message, where the first message is used to request to establish the RRC connection, where the first message includes the first cause value.
  • processing module 901 is further configured to:
  • processing module 901 is further configured to:
  • the first cause value is determined according to the mapping relationship between the AI and the first cause value.
  • processing module 901 is further configured to:
  • the first cause value is determined according to the mapping relationship between the AC and the first cause value.
  • processing module 901 is further configured to:
  • the first cause value is determined by the first protocol layer according to the access information.
  • processing module 901 is further configured to:
  • the first cause value is obtained by the second protocol layer from the first protocol layer.
  • the first message including the first cause value described above is transmitted by the second protocol layer.
  • processing module 901 is further configured to:
  • the access information is obtained by the second protocol layer from the first protocol layer.
  • the first cause value is determined by the second protocol layer according to the access information.
  • the foregoing first radio access technology includes an E-UTRA technology
  • the second radio access technology includes an NR technology.
  • the first protocol layer is a NAS
  • the second protocol layer is an RRC layer.
  • the foregoing communication device may further include a transceiver, configured to support the foregoing communications device to perform data transmission, signaling, or information in the foregoing method embodiment, for example, sending the first message.
  • a transceiver configured to support the foregoing communications device to perform data transmission, signaling, or information in the foregoing method embodiment, for example, sending the first message.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)).
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a DVD
  • a semiconductor medium e.g., a Solid State Disk (SSD)
  • 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 Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种通信方法及装置，该方法包括：终端首先确定建立RRC连接使用的第一无线接入技术，进而，终端根据接入信息确定建立该RRC连接的第一原因值，其中，该第一原因值是上述第一无线接入技术的原因值，该接入信息包括接入标识AI、接入类别AC和第二无线接入技术的第二原因值中的至少一种。当终端确定出第一原因值之后，终端发送用于建立上述RRC连接的第一消息，并在该第一消息中携带该第一原因值。使用该方法，实现了终端使用一种无线接入技术接入多种核心网时，可以正常的进行原因值的上报。

Description

通信方法及装置
本申请要求于2018年5月11日提交中国专利局、申请号为2018104514360、申请名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，尤其涉及一种通信方法及装置。
背景技术
随着无线通信技术的演进，未来无线网络系统中可以包含多种无线接入技术，例如第二代(2rd Generation，2G)无线通信技术、第三代(3rd Generation，3G)无线通信技术、第四代(4rd Generation，4G)无线通信技术、第五代(5rd Generation，5G)无线通信技术以及未来进一步演进的无线接入技术中的一种或多种。另外，未来无线网络系统中还可以包含非3GPP组织定义的无线接入技术，例如无线局域网(Wireless LAN，WLAN)、蓝牙、短距离通信技术等。同时，支持一种或多种无线接入技术的无线接入网设备可以与多个使用不同技术的核心网连接，核心网类型可以为2G核心网、3G核心网、4G核心网(The Evolved Packet Core，EPC)、5G核心网(5G Core，5GC)、以及未来进一步演进的核心网类型等。此外，由于业务类型越来越丰富，终端和无线接入网设备的能力也越来越强大，因此当终端与无线接入网设备建立连接时，希望终端能够提供更多的连接建立原因值，用于无线接入网进行处理和网络优化。
当无线接入设备通过一种无线接入技术为终端提供多个使用不同技术的核心网的服务时，与多个核心网所属的无线通信系统对应的原因值需要承载在同一个无线接入技术定义的消息格式中。
因此，需要提供一种对原因值进行处理的方法，以实现终端使用相同的无线接入技术接入不同核心网时，可以正常的进行原因值的上报。
发明内容
本申请提供一种通信方法及装置，以使得终端通过一种无线接入技术接入不同核心网时，可以正常的进行原因值的上报。
本申请第一方面提供一种通信方法，该方法包括：
终端首先确定建立RRC连接使用的第一无线接入技术，进而，终端根据接入信息确定建立该RRC连接的第一原因值，其中，该第一原因值是上述第一无线接入技术的原因值，该接入信息包括接入标识AI、接入类别AC和第二无线接入技术的第二原因值中的至少一种。当终端确定出第一原因值之后，终端发送用于建立上述RRC连接的第一消息，并在该第一消息中携带该第一原因值。
在该方法中，终端根据包括AI、AC以及第二原因值中至少一种的接入消息可以确定第一原因值，其中，第一原因值为第一无线接入技术的原因值，第二原因值为第二无线接 入技术的原因值。从而使得在无线接入设备通过一种无线接入技术为终端提供多个使用不同技术的核心网的服务时，终端向无线接入设备发送的与不同核心网通信的原因值可以承载在同一个无线接入技术定义的消息格式中。从而实现了终端使用一种的无线接入技术接入多种核心网时，可以正常的进行原因值的上报。例如，当终端通过ng-eNB接入EPC时，使用E-UTRA的第一原因值，当终端通过ng-eNB接入5GC时，对应的第一无线接入技术为E-UTRA，第二无线接入技术为NR，则终端可以根据AI、AC以及NR的原因值中的至少一种确定出E-UTRA原因值，即终端在接入5GC时，同样可以使用E-UTRA向ng-eNB上报原因值，从而保证终端通过ng-eNB连接EPC以及5GC时都可以正常上报原因值。
在一种可能的设计中，终端可以根据上述第二原因值与第一原因值的映射关系，确定上述第一原因值。
在一种可能的设计中，终端可以根据AI与上述第一原因值的映射关系，确定上述第一原因值。
在一种可能的设计中，终端可以根据AC与上述第一原因值的映射关系，确定上述第一原因值。
在一种可能的设计中，可以由终端的第一协议层根据上述接入信息，确定上述第一原因值。
在一种可能的设计中，可以由终端的第二协议层从终端的第一协议层获取上述第一原因值，并由第二协议层发送包含上述第一原因值的第一消息。
在一种可能的设计中，可以由终端的第二协议层从终端的第一协议层获取上述接入信息，并由终端的第二协议层根据上述接入信息，确定上述第一原因值。
在一种可能的设计中，上述第一无线接入技术包括全球陆地无线接入E-UTRA技术，所述第二无线接入技术包括新空口NR技术。
在一种可能的设计中，上述第一协议层为非接入层NAS，所述第二协议层为RRC层。
在一种可能的设计中，上述建立RRC连接包括新建RRC连接、恢复RRC连接或者重建RRC连接。
在一种可能的设计中，上述第二原因值与第一原因值的映射关系可以预先通过以下任意一种方式配置：
NAS信令消息配置、操作管理维护OAM配置、运营商预配置、默认配置。
在一种可能的设计中，上述AI与第一原因值的映射关系可以预先通过以下任意一种方式配置：
NAS信令消息配置、操作管理维护OAM配置、运营商预配置、默认配置。
在一种可能的设计中，上述AC与第一原因值的映射关系可以预先通过以下任意一种方式配置：
NAS信令消息配置、操作管理维护OAM配置、运营商预配置、默认配置。
本申请第二方面提供一种通信装置，该通信装置包括处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现上述第一方面中的方法。可选的，所述通信装置还可以包括收发器，用于支持所述通信装置执行上述第一方面方法中收发数据、信令或信息，例如，发送第一消息。可选的，该通信装置可以是一种终端设备，也可是终 端设备中的一部分装置，例如终端设备中的芯片系统。可选的，所述芯片系统，用于支持终端设备实现上述方面中所涉及的功能，例如，生成，接收，发送，或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的程序指令和数据。该芯片系统，包括芯片，也可以包括其他分立器件或电路结构。
本申请第三方面提供一种通信装置，该通信装置有实现第一方面中的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，该电子设备可以包括处理模块和发送模块，该处理模块和发送模块可以执行上述方法中的相应功能，例如：处理模块，用于确定建立RRC连接使用的第一无线接入技术，以及根据接入信息确定建立所述RRC连接的第一原因值，所述接入信息包括AI、AC和第二无线接入技术的第二原因值中的至少一种；发送模块，用于发送第一消息，所述第一消息用于请求建立所述RRC连接，所述第一消息中包括所述第一原因值。
本申请第四方面提供一种可读存储介质，所述存储介质存储有计算机程序，所述计算机程序包括用于执行上述第一面所述的方法的指令。
本申请第五方面提供一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码被执行时，使得计算机执行第一方面所述的方法。
需要说明的是，上述计算机程序代码可以全部或者部分存储在第一存储介质上，其中第一存储介质可以与处理器封装在一起的，也可以与处理器单独封装，本申请实施例对此不作具体限定。
附图说明
图1为5G无线通信系统的系统架构图；
图2为ng-eNB同时连接至5GC和EPC的连接示意图；
图3为一个支持两种无线接入技术的终端的协议栈以及与ng-eNB连接的架构图；
图4为本申请提供的通信方法实施例一的流程示意图；
图5为本申请提供的通信方法的第一交互流程图；
图6为本申请提供的通信方法的第二交互流程图；
图7为本申请提供的通信方法的第三交互流程图；
图8为本申请提供的通信装置的实体框图；
图9为本申请提供的通信装置的模块结构图。
具体实施方式
首先，应理解，本申请实施例中所述的至少一个表示“一个”或“一个以上”。示例性的，包括A、B、C中的至少一个，可能表示如下含义：
(1)包括A
(2)包括B
(3)包括C
(4)包括A和B
(5)包括A和C
(6)包括B和C
(7)包括A、B和C
在无线通信接入技术的演进过程中，各种无线接入技术不断出现，例如2G、3G、4G、5G等无线接入技术。以4G和5G为例，4G无线通信系统基于过全球陆地无线接入(Evolved-UMTS Terrestrial Radio Access，E-UTRA)技术进行通信，5G无线通信系统(5G System，5GS)基于新空口(New Radio，NR)技术进行通信。终端在与无线接入网设备连接时，可以使用一种或多种无线接入技术进行连接。例如，不同终端可以分别使用NR以及E-UTRA接入5G核心网，因此，不同的终端使用的NAS层均为5GS NAS，使用的RRC层为对应的NR RRC或E-UTRA RRC。
本申请所提供的技术方案可以应用于上述的无线接入技术以及上述之外的各种无线接入技术。为便于描述，本申请以下实施例以5G系统的NR技术以及4G系统的E-UTRA技术为例进行说明，但本申请并不以此为限。
图1为5G无线通信系统的系统架构图，如图1所示，主要由5GC和5G RAN(又称为NG-RAN)组成，其中，5GC为5GS的核心网，其中可以包括接入和移动性管理功能(Access and Mobility Management Function，AMF)和用户平面功能(User Plane Function，UPF)等网元。5G RAN为5G无线通信系统的无线接入网。在5G RAN中，存在两种类型的RAN节点，分别为gNB和ng-eNB。gNB为终端提供NR的用户面和控制面协议栈的终结点。ng-eNB为终端提供演进的E-UTRA的用户面和控制面协议栈的终结点。对于ng-eNB而言，其可以与5GC相连，使终端通过ng-eNB接入5GC，同时，其也可以与4G的EPC相连，使终端通过该ng-eNB接入EPC。
当ng-eNB与5GC相连时，ng-eNB E-UTRA技术为终端提供无线传输资源，并为终端提供5GC的服务。
在实际部署中，ng-eNB可以仅与5GC或者EPC相连，或者ng-eNB可以同时连接5GC和EPC。图2为ng-eNB同时连接至5GC和EPC的连接示意图，如图2所示，ng-eNB同时连接至5GC和EPC。除此之外，终端还可以通过传统eNB接入EPC，通过gNB接入5GC。具体的，ng-eNB与gNB均与5GC相连接，终端可以通过ng-eNB或者gNB接入5GC。ng-eNB与gNB之间可以相连，用于基站间通信，以及交互与终端相关的信息。同时，当网络中还有传统的eNB时，ng-eNB与eNB之间相连，用于基站间的通信，以及交互与终端相关的信息。传统的LTE终端可以通过eNB或ng-eNB接入EPC。
由上述可知，对于一个终端来说，既可以通过gNB接入5GC，也可以通过ng-eNB接入5GC。而对于ng-eNB来说，既可以与5GC连接，也可以与EPC连接。
图3为一个支持两种无线接入技术的终端的协议栈以及与ng-eNB连接的架构图，如图3所示，该终端同时支持NR技术和E-UTRA技术，即既可以接入5GC，也可以接入EPC。假设该终端同时支持通过gNB和ng-eNB接入5GC，则如图3所示，该终端支持NR的空口协议栈，例如包括NR RRC协议层，NR底层协议层(如RLC，MAC，PHY层)，以及为5GS定义的非接入层(Non-Access Stratum，NAS)，简称5GS NAS协议层。同 时，该终端还支持E-UTRA的空口协议栈，例如包括E-UTRA RRC，E-UTRA底层协议层，以及5GS NAS协议层。另外，假设该终端支持通过ng-eNB或eNB接入EPC，则该终端还需要支持为EPS定义的NAS协议层，简称EPS NAS。如果终端支持一种接入方式，则在终端内部需要支持对应的协议栈。即，若终端具备通过E-UTRA接入5GC的能力，则该终端需要至少具备5GS NAS协议层和E-UTRA RRC协议层；若终端具备通过NR接入5GC的能力，则该终端需要至少具备5GS NAS协议层和NR RRC协议层；若终端具备通过E-UTRA接入EPC的能力，则该终端需要至少具备EPS NAS协议层和E-UTRA RRC协议层。需要说明的是，图3仅支持两种无线接入技术的终端作为示例，但是本申请实施例同样适用于支持一种无线接入技术的终端。例如，当终端不具有图3所示的NR RRC协议层以及NR底层时，同样可以应用本申请实施例的技术方案。以及，当终端不具有图3所示的EPS NAS时，同样可以应用本申请实施例的技术方案。
需要说明的是，本申请的技术方案，主要针对终端通过ng-eNB接入5GC的场景，但是，为便于本领域技术人员更好地理解本申请的技术方案，本申请以下实施例中也会对终端通过gNB的过程进行描述。
现有的终端在向核心网(例如5GC或EPC)发送信令或数据之前，需要首先向基站(例如gNB或ng-eNB)发送RRC请求，以建立RRC连接。在发送RRC请求时，终端在RRC请求中携带原因值，用来标识终端本次接入的原因。上述RRC请求可以用于请求新建RRC连接或者恢复RRC连接。所述恢复RRC连接，可以为UE从第三态(或称为非活跃(inactive)态)转换为连接态时，将挂起的RRC连接恢复为能够正常通信的RRC连接。对应的，具体的RRC消息可以为RRC连接请求(即RRC Connection Request)、RRC建立请求(即RRC Setup Request)、RRC恢复请求(即RRC Resume Request)、RRC连接恢复请求(即RRC Connection Resume Request)等。
在现有技术中，LTE相关协议规定的RRC请求中的原因值共占用3个比特，最多可携带8种取值，当前协议规定了7种原因值(不排除在LTE系统的未来演进中，会定义多于7个原因值，例如8个)，分别为：紧急业务(即emergency)，高优先级接入(即highPriorityAccess)，终端终止的接入(mobile terminating access，mt-Access)，终端发起的信令(mobile originating signalling，mo-Signalling)，终端发起的数据(mobile originating data，mo-Data)，时延容忍的接入(即delayTolerantAccess)，终端发起的语音电话(mobile originating voice call，mo-VoiceCall)。
而对于5GS而言，出于其对诸如视频等业务上的更高要求等原因，可供终端在RRC请求中携带的原因值的数量可能会多于EPS系统中规定的7个，例如可能为8个或者多于8个。如果5GS中规定的原因值的数量较多，则需要在RRC请求中占用更多的字段来携带原因值。
参照图3中的协议栈示意，现有技术中，终端接入5GC时发送的RRC请求中的原因值由5GS NAS生成，再携带在RRC消息中进而由下层协议栈发出。如果终端通过gNB接入5GC，则终端向gNB发送RRC请求。一种可能的情况是，由于gNB是通过NR技术为终端提供无线传输资源的，NR作为新空口，可以定义新的RRC消息格式，因此，可以直接使用相比EPS中更多的字段来携带原因值。
但是，如果终端通过ng-eNB接入5GC，终端需要向ng-eNB发送RRC请求。如前所 述，ng-eNB通过E-UTRA技术为终端提供无线传输资源，因此，RRC请求中的原因值所占的字段长度需要遵循E-UTRA协议中的规定，即原因值的数量为7个(最多为8个)。在这种情况下，如果终端在向ng-eNB发送RRC请求之前，不对原因值进行相应处理，就会导致原因值发送出现异常。
本申请所述的技术方案，旨在解决上述问题。
需要说明的是，本申请以下实施例所述的终端是任何可以通过ng-eNB接入5GC的终端。应理解，在本申请实施例中，终端可以包括但不限于应用于物联网中的终端设备，例如，可以是接入NB-IoT中的终端设备(可以称为“NB-IoT终端”)：智能抄表设备、物流追踪设备、环境监测设备等；该终端还可以包括但不限于移动台(Mobile Station，MS)、移动终端(Mobile Terminal)、移动电话(Mobile Telephone)、用户设备(User Equipment，UE)、手机(handset)及便携设备(portable equipment)等，该终端设备可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，例如，终端设备可以是移动电话(或称为“蜂窝”电话)、具有无线通信功能的计算机等，终端设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置。
图4为本申请提供的通信方法实施例一的流程示意图，如图4所示，该方法包括：
S401、可选的，终端确定建立RRC连接使用的第一无线接入技术。
可选的，终端的第一协议层可以从第二协议层获取建立RRC连接所使用的第一无线接入技术。
可选的，上述第一协议层可以是NAS，上述第二协议层可以是RRC层。
示例性的，上述第一协议层具体可以是图3所示例的5GS NAS，上述第二协议层可以是图3所示例的E-UTRA RRC。
为便于描述，本申请以下实施例以第一协议层为5GS NAS，上述第二协议层为E-UTRA RRC为例进行说明。但是，需要说明的是，本申请并不以此为限，上述第一协议层和上述第二协议层还可以是其他无线通信系统或接入技术的协议层。
可选的，上述第一无线接入技术可以是E-UTRA。
S402、终端根据接入信息确定建立上述RRC连接的第一原因值，该第一原因值是上述第一无线接入技术的原因值，该接入信息包括接入标识(Access Identity，AI)、接入类别(Access Category，AC)和第二无线接入技术的第二原因值中的至少一种。
其中，上述接入信息包括AI、AC和第二无线接入技术的第二原因值中的至少一种，具体包括以下几种情况：
(1)接入信息包括AI
(2)接入信息包括AC
(3)接入信息包括第二原因值
(4)接入信息包括AI和AC
(5)接入信息包括AI和第二原因值
(6)接入信息包括AC和第二原因值
(7)接入信息包括AI、AC和第二原因值
可选的，上述AI和AC获取过程可以如下：
5GS NAS实时检测由如下事件之一触发的接入尝试(access attempt)是否发生：
(1)、需要终端从5G移动管理(Mobility Management，MM)空闲状态(5G MM-IDLE)转换为5GMM连接状态(5GMM-CONNECTED)的事件
(2)终端在5GMM连接状态或者在5GMM连接状态(同时具有RRC第三状态指示)下发生如下事件：
A、5GMM从上层收到语音电话启动指示(即MO-MMTEL-voice-call-started indication)，视频电话启动指示(即MO-MMTEL-video-call-started indication)或者SMS over IP启动指示(即MO-SMSoIP-attempt-started indication)等
B、5GMM从上层收到终端发起的SMS over NAS的请求(除了该请求触发的业务请求流程需要将UE从5GMM空闲态转换为5GMM连接态的情况)等
C、5GMM从上层收到UL NAS TRANSPORT消息用于协议数据单元(Protocol Data Unit，PDU)会话的建立(除了该请求触发的业务请求流程需要将UE从5GMM空闲态转换为5GMM连接态的情况)
D、5GMM从上层收到UL NAS TRANSPORT消息用于PDU会话的修改(除了该请求触发的业务请求流程需要将UE从5GMM空闲态转换为5GMM连接态的情况)
E、5GMM从上层收到用于重建现有PDU会话的用户面资源的请求
当5GS NAS检测出上述事件之一发生时，根据预设的映射关系得到至少一个AI以及一个AC。
上述预设的映射关系具体可以是协议中规定的映射关系。
其中，AI可以由AI标识或索引值来区分，例如，AI0和AI1分别标识特定含义的AI。相应的，AC也可以由AC标识或索引值来区分，例如，AC0和AC1分别标识特定含义的AC。
示例性的，如果终端被配置了多媒体优先业务(Multimedia Priority Service,MPS)的，5GS NAS映射为AI1，如果终端被配置了多媒体优先业务(Multimedia Priority Service,MPS)的终端，5GS NAS映射为AI1，如果关键任务业务(Mission Critical Service,MCS)，5GS NAS映射为AI2。
示例性的，如果接入尝试的类型是对寻呼(paging)的响应，则5GS NAS映射为AC0，如果接入尝试的类型是紧急呼叫，则5GS NAS映射为AC2。
可选的，上述第二原因值的获取过程为：
5GS NAS根据AI、AC以及接入尝试的类型中的至少一种确定上述第二原因值。
其中，上述接入尝试类型用于标识呼叫类型。示例性的，接入尝试类型可以是紧急呼叫、对寻呼的响应或者是终端发起的视频电话等。
上述第二原因值为第二无线接入技术的建立原因值，可选的，上述第二无线接入技术可以是NR。
示例性的，5GS NAS基于下述表一获取第二原因值。其中，AI的取值包含AI0，AI1，…，AIX，AC的取值包含AC0，AC1，…，ACY，第二原因值(即表中的RRC建立原因值)包含N个不同的取值。其中，X为大于0的整数，Y为大于0的整数，N为大于0的整数。
表一
Figure PCTCN2019086208-appb-000001
Figure PCTCN2019086208-appb-000002
进而，在获取到上述AI、AC以及第二原因值之后，终端即可以根据这三者中的至少一种来确定第一原因值。
可选的，终端可以通过以下三种方式来确定第一原因值：
(1)终端根据上述第二原因值与第一原因值的映射关系，确定第一原因值。
示例性的，第二原因值与第一原因值的映射关系可以为下述表二中定义的表现形式。其中，第一原因值具有M个不同的取值，其中M为大于0的整数，并且M小于N。
表二
第二原因值 第一原因值
第二原因值的第一取值 M个第一原因值的其中一个取值
第二原因值的第二取值 M个第一原因值的其中一个取值
… M个第一原因值的其中一个取值
第二原因值的第N取值 M个第一原因值的其中一个取值
可选的，一种可能的实施方式是，全部第一原因值中的取值均与第二原因值中的取值相同，第二原因值中有N-M个第一原因值中不具有的取值，此时多于1个不同的第二原因值中的取值会对应相同的第一原因值中的一个取值。此时，表二也可以仅包含N-M个第一原因值中不具有的第二原因值的取值与第一原因值的取值的映射关系。例如，第二原因值的第k取值(其中k大于等于1，小于等于N)为用于指示视频业务的原因值，第一原因值中不包含该取值，则表二可以指示将第二原因值的第k取值映射为第一原因值的第L取值(例如指示语音业务的原因值，可以为终端发起的语音电话原因值)，参见下述表二-1。
表二-1
第二原因值(共N-M个) 第一原因值
第二原因值的第k取值 M个第一原因值的其中一个取值(例
  如第L取值)
… M个第一原因值的其中一个取值
(2)终端根据上述AI与上述第一原因值的映射关系，确定第一原因值。
(3)终端根据上述AC与上述第一原因值的映射关系，确定第一原因值。
以方式(1)中终端根据上述第二原因值与第一原因值的映射关系，确定第一原因值为例，第二原因值与第一原因值的映射关系可以通过以下任意一种方式来建立：
核心网通过NAS信令消息将上述映射关系发送给终端、操作管理维护(Operation Administration and Maintenance，OAM)配置将上述映射关系发送给终端、运营商预配置、默认配置
其中，上述运营商预配置例如可以是由运营商预先将配置信息写入终端的设备上，或者是由运营商预先将配置信息写入全球用户识别卡(Universal Subscriber Identity Module，USIM)中，当该USIM卡被插入到终端之后，终端即获取到配置信息。
上述默认配置例如可以是由协议规定的配置，例如可以是在5GS NAS的协议或者E-UTRA RRC协议中规定上述第二原因值与第一原因值的映射关系。
AI与第一原因值的映射关系，以及AC与第一原因值的映射关系也可以通过上述任意一种方式来建立，不再赘述。
另外需要说明的是，终端除了根据AI、AC以及第二原因值中的至少一种来确定第一原因值外，可选的，还可以根据接入尝试类型来确定第一原因值。
在具体实施过程中，上述确定第一原因值的方法可以分别实施，也可以结合起来实施。当结合实施时，示例性的，终端可以同时根据AI与第一原因值的映射关系以及AC与第一原因值的映射关系来确定第一原因值，此时一种可能的实施方式是终端获取一份映射关系，即AI和AC与第一原因值的映射关系，从而确定第一原因值。其中，AI和AC与第一原因值的映射关系可以参照与表一类似的方式定义，如下述表三所示。
表三
Figure PCTCN2019086208-appb-000003
Figure PCTCN2019086208-appb-000004
可选的，一种可能的实施方式是，全部第一原因值中的取值均与第二原因值中的取值相同，第二原因值中有N-M个第一原因值中不具有的取值，此时表三中的一部分映射关系与表一种的映射关系完全相同，则表三中也可以仅包含与表一中不同的部分，如下述表三-1所示，当依据表一得到的第二原因值是第一原因值中的一个取值，表三-1中不需要携带AI和AC与该第一原因值的取值的映射关系。
表三-1
Figure PCTCN2019086208-appb-000005
以下从不同执行主体的角度说明本申请的可选实施方式。
参照图3所示的终端协议栈结构，终端上包括第一协议层和第二协议层，其中，第一协议层例如可以是NAS，第二协议层例如可以是RRC层。在现有技术中，以终端通过gNB接入5GC为例，首先由终端的5GS NAS生成NR原因值，进而，5GS NAS将NR原因值发送给NR RRC，并由NR RRC再发送给gNB。
而本步骤中，终端可以使用以下两种可选方式来执行：
(1)由第一协议层根据上述接入信息确定第一原因值
具体的，第一协议层可以通过上述的任意一种映射方式或其组合来确定第一原因值。
示例性的，第一协议层为5GS NAS，终端根据AI和AC与第一原因值的映射关系来确定第一原因值。则该方式的具体执行过程为：
5GS NAS首先获取AI和AC，进而，5GS NAS基于AI和AC与第一原因值的映射关系，得到第一原因值。
相应的，针对本实施方式，进一步的，5GS NAS将第一原因值发送给E-UTRA RRC，由E-UTRA RRC直接发送给ng-eNB。即，由第二协议层从第一协议层获取第一原因值，再发送包含第一原因值的第一消息。
(2)由第二协议层根据上述接入信息确定第一原因值
在该方式中，第二协议层首先从第一协议层获取上述接入信息，进而，再根据上述接入信息确定第一原因值。
具体的，第一协议层向第二协议层发送AI、AC以及第二接入技术的第二原因值中的至少一种，可选的，第一协议层还可以向第二协议层发送接入尝试的类型。第二协议层接收到这些信息后，可以通过上述的任意一种映射方式或其组合来确定第一原因值。
示例性的，第一协议层为5GS NAS，终端根据AI和AC与第一原因值的映射关系来确定第一原因值。则该方式的具体执行过程为：
5GS NAS首先获取AI和AC，进而，5GS NAS将AI和AC发送给E-UTRA RRC。 E-UTRA RRC接收到AI和AC后，基于AI和AC与第一原因值的映射关系，得到第一原因值。
可选的，第一协议层向第二协议层发送AI、AC以及第二接入技术的第二原因值中的至少一种时，可以按照如下方式来发送：
(1)第一协议层确定出与第二无线接入技术对应的第二原因值，第一协议层将第二原因值发送给第一无线接入技术的第二协议层。
(2)如果第一协议层确定终端使用的无线接入技术(Radio Access Technology，RAT)为第一无线接入技术，第一协议层直接将AI和AC发送给第二协议层。
(3)如果第一协议层确定终端使用的无线接入技术(Radio Access Technology，RAT)为第一无线接入技术，第一协议层确定出与第二无线接入技术对应的第二原因值，当该第二原因值不属于第一接入技术的第一原因值的一种取值时，则第一协议层直接将AI和AC发送给第二协议层。如果第一协议层所确定出的第二原因值属于第一无线接入技术的第一原因值的一种取值时，则第一协议层直接将第二原因值发送给第二协议层，作为第一无线接入技术的第一原因值。示例性的，第一协议层生成第二原因值，当第一原因值的取值中包含该第二原因值时，第一协议层将该第二原因值作为第一原因值发送给第二协议层，用于第二协议层携带在第一消息中；当第一原因值的取值中不包含该第二原因值时，第一协议层将AI和AC发送给第二协议层，用于第二协议层基于该AI和AC获取第一原因值(例如按照表三-1所示的映射关系)。
S403、终端发送第一消息，该第一消息用于请求建立RRC连接，该第一消息中包括所述第一原因值。
具体的，当终端通过上述步骤确定出第一原因值后，将该第一原因值携带在第一消息中发送出去。
可选的，上述第一消息可以是新建RRC连接的消息、恢复RRC连接的消息或重建RRC连接的消息。其中，新建RRC连接的消息可以为RRC连接请求消息(RRC Connection Request)，恢复RRC连接的消息可以是RRC连接恢复请求消息(RRC Connection Resume Request)，重建RRC连接的消息可以是RRC连接重建请求消息(RRC Connection Reestablishment Request)。
本实施例中，终端根据包括AI、AC以及第二原因值中至少一种的接入消息可以确定第一原因值，其中，第一原因值为第一无线接入技术的原因值，第二原因值为第二无线接入技术的原因值。从而使得在无线接入设备通过一种无线接入技术为终端提供多个使用不同技术的核心网的服务时，终端向无线接入设备发送的与不同核心网通信的原因值可以承载在同一个无线接入技术定义的消息格式中。从而实现了终端使用一种的无线接入技术接入多种核心网时，可以正常的进行原因值的上报。例如，当终端通过ng-eNB接入EPC时，使用E-UTRA的第一原因值，当终端通过ng-eNB接入5GC时，对应的第一无线接入技术为E-UTRA，第二无线接入技术为NR，则终端可以根据AI、AC以及NR的原因值中的至少一种确定出E-UTRA原因值，即终端在接入5GC时，同样可以使用E-UTRA向ng-eNB上报原因值，从而保证终端通过ng-eNB连接EPC以及5GC时都可以正常上报原因值。
本申请以下以第一无线接入技术为E-UTRA，第二无线接入技术为NR，第一协议层 为5GS NAS，第二协议层为E-UTRA RRC为例，来说明本申请的完整执行过程。
图5为本申请提供的通信方法的第一交互流程图，如图5所示，第一原因值由5GS NAS生成并发送给E-UTRA RRC，具体执行过程为：
S501、可选的，5GS NAS获取RRC层的无线接入技术。在该步骤之前，终端已经执行过小区选择或小区重选，并驻留在一个小区中。此时，上述RRC层的无线接入技术是指终端所驻留小区所使用的无线接入技术。示例性的，终端驻留在E-UTRA小区中，则RRC层的无线接入技术为E-UTRA。
需要说明的是，此时5GS NAS已经处于工作状态，因此该终端接入的RAN为NG-RAN。因为NG-RAN中能够提供两种无线接入技术，即NR和E-UTRA，因此5GS NAS可知RRC层对应的无线接入技术为NR或E-UTRA。若5GS NAS的功能包括为NR的RRC和E-UTRA的RRC提供不同的参数(例如原因值)，则5GS NAS需要获取RRC层的无线接入技术是NR还是E-UTRA。若5GS NAS为RRC提供一致的服务(即无需区分NR和E-UTRA的RRC)则5GS NAS无需进一步获取RRC层的无线接入技术是NR还是E-UTRA。
S502、5GS NAS向RRC层发送请求，以触发RRC层进行RRC连接建立。
S503、5GS NAS确定RRC层的无线接入技术为E-UTRA。
S504、5GS NAS根据AI、AC以及接入尝试类型中的至少一种确定NR的原因值(第二原因值)。
具体的，5GS NAS可以根据图4所示的实施例中的具体方法确定NR的原因值。
示例性的，5GS NAS按照表一确定第二原因值。
S505、5GS NAS根据AI、AC、第二原因值以及接入尝试类型中的至少一种确定E-UTRA的原因值(第一原因值)。
具体的，5GS NAS可以根据图4所示的实施例中的具体方法确定E-UTRA的原因值。
示例性的，5GS NAS按照表二、表二-1、表三、或表三-1确定第一原因值。需要说明的是，S504为可选步骤。例如，如果5GS NAS仅根据AI和AC确定第一原因值，则不需要执行S504。
S506、5GS NAS向E-UTRA RRC层发送AI、AC以及E-UTRA的原因值。
S507、E-UTRA RRC层读取驻留小区系统消息(System Information)，获取其中的接入控制参数。
示例性的，上述接入控制参数包含与AC相关的接入比例和禁止时间，以及与AI相关的比特图(Bitmap)。
S508、E-UTRA RRC层根据AI、AC和上述接入控制参数判断小区是否为禁止状态(barred)。若为禁止状态，则执行S509，若不为禁止状态，则执行S510。
S509、E-UTRA RRC层向5GS NAS发送用于指示NAS层接入禁止的指示信息。
S510、E-UTRA RRC层向ng-eNB发送RRC消息。
该RRC消息统称为消息3(Message3，MSG3)。MSG3中携带E-UTRA的原因值，用于指示ng-eNB该终端发起连接建立或恢复的原因。
S511、ng-eNB接收MSG3，获取其中E-UTRA的原因值。
S512、ng-eNB判断是否允许该终端的接入，并回复消息4(Message4，MSG4)。
若允许接入，则MSG4中携带表示允许接入的RRC消息，例如可以是RRC Connection  Setup，RRC Connection Resume。
若不允许接入，则MSG4中携带表示拒绝的RRC消息，例如可以是RRC Connection Reject，RRC Connection Resume Reject。
进一步的，可选的，ng-eNB将该E-UTRA的原因值发送给5GC的网元(例如AMF)，用于辅助5GC进行针对该终端的接入控制。
图6为本申请提供的通信方法的第二交互流程图，如图6所示，第一原因值由5GS NAS生成并发送给E-UTRA RRC，具体执行过程为：
S601、5GS NAS获取RRC层的无线接入技术。
在该步骤之前，终端已经执行过小区选择或小区重选，并驻留在一个小区中。
S602、5GS NAS向RRC层发送Access Attempt，以触发RRC层进行RRC连接建立、RRC连接回复或RRC连接重建。
S603、5GS NAS确定RRC层的无线接入技术为E-UTRA。
S604、5GS NAS根据AI、AC以及接入尝试类型中的至少一种确定NR的原因值(第二原因值)。
具体的，5GS NAS可以根据图4所示的实施例中的具体方法确定NR的原因值。
示例性的，5GS NAS按照表一确定第二原因值。
S605、5GS NAS向E-UTRA RRC层发送AI、AC以及NR的原因值。
需要说明的是，S604为可选步骤。例如，如果E-UTRA RRC层无需使用NR的原因值确定第一原因值，则不需要执行S504，并且，在本步骤中，5GS NAS也不需要向E-UTRA RRC层发送NR的原因值。
S606、E-UTRA RRC层读取驻留小区系统消息(System Information)，获取其中的接入控制参数。
示例性的，上述接入控制参数包含与AC相关的接入比例和禁止时间，以及与AI相关的比特图(Bitmap)。
S607、E-UTRA RRC层根据AI、AC和上述接入控制参数判断小区是否为禁止状态(barred)。若为禁止状态，则执行S608，若不为禁止状态，则执行S609及S610。
S608、E-UTRA RRC层向5GS NAS发送用于指示NAS层接入禁止的指示信息。
S609、E-UTRA RRC层根据AI、AC、NR的原因值以及接入尝试类型中的至少一种确定E-UTRA的原因值。可选的，该步骤S609可以发生在步骤S605与步骤S607之间。
具体的，E-UTRA RRC层可以根据图4所示的实施例中的具体方法确定E-UTRA的原因值。
示例性的，E-UTRA RRC按照表二、表二-1、表三、或表三-1确定第一原因值。
S610、E-UTRA RRC层向ng-eNB发送RRC消息。
该RRC消息统称为MSG3。MSG3中携带E-UTRA的原因值，用于指示ng-eNB该终端发起RRC连接建立或恢复的原因。
S611、ng-eNB接收MSG3，获取其中E-UTRA的原因值。
S612、ng-eNB判断是否允许该终端的接入，并回复MSG4。
若允许接入，则MSG4中携带表示允许接入的RRC消息，例如可以是RRC Connection Setup，RRC Connection Resume。
若不允许接入，则MSG4中携带表示拒绝的RRC消息，例如可以是RRC Connection Reject，RRC Connection Resume Reject。
进一步的，可选的，ng-eNB将该E-UTRA的原因值发送给5GC的网元(例如AMF)，用于辅助5GC进行针对该终端的接入控制。
为使本申请的技术方案更加清楚，以下对终端通过gNB接入5GC的过程进行说明。
图7为本申请提供的通信方法的第三交互流程图，如图7所示，终端通过gNB接入5GC的具体过程为：
S701、可选的，5GS NAS获取RRC层的无线接入技术。
在该步骤之前，终端已经执行过小区选择或小区重选，并驻留在一个小区中。此时，上述RRC层的无线接入技术是指终端所驻留小区所使用的无线接入技术。示例性的，终端驻留在E-UTRA小区中，则RRC层的无线接入技术为E-UTRA。
需要说明的是，此时5GS NAS已经处于工作状态，因此该终端接入的RAN为NG-RAN。因为NG-RAN中能够提供两种无线接入技术，即NR和E-UTRA，因此5GS NAS可知RRC层对应的无线接入技术为NR或E-UTRA。若5GS NAS的功能包括为NR的RRC和E-UTRA的RRC提供不同的参数(例如原因值)，则5GS NAS需要获取RRC层的无线接入技术是NR还是E-UTRA。若5GS NAS为RRC提供一致的服务(即无需区分NR和E-UTRA的RRC)则5GS NAS无需进一步获取RRC层的无线接入技术是NR还是E-UTRA。
S702、5GS NAS向RRC层发送请求，以触发RRC层进行RRC连接建立、RRC连接回复或RRC连接重建。
S703、5GS NAS根据AI、AC以及接入尝试类型中的至少一种确定NR的原因值。示例性的，5GS NAS按照表一确定第二原因值。
具体的，5GS NAS可以根据图4所示的实施例中的具体方法确定NR的原因值。
S704、5GS NAS向NR RRC层发送AI、AC以及NR的原因值。
S705、NR RRC层读取驻留小区系统消息(System Information)，获取其中的接入控制参数。
示例性的，上述接入控制参数包含与AC相关的接入比例和禁止时间，以及与AI相关的比特图(Bitmap)。
S706、NR RRC层根据AI、AC和上述接入控制参数判断小区是否为禁止状态(barred)。若为禁止状态，则执行S707，若不为禁止状态，则执行S708及S709。
S707、NR RRC层向5GS NAS发送用于指示NAS层接入禁止的指示信息。
S708、NR RRC层向gNB发送RRC消息。
该RRC消息统称为MSG3。MSG3中携带NR的原因值，用于指示gNB该终端发起连接建立或恢复的原因。
S709、gNB接收MSG3，获取其中的NR的原因值。
S710、gNB判断是否允许该终端的接入，并回复MSG4。
若允许接入，则MSG4中携带表示允许接入的RRC消息，例如可以是RRC Connection Setup，RRC Connection Resume。
若不允许接入，则MSG4中携带表示拒绝的RRC消息，例如可以是RRC Connection Reject，RRC Connection Resume Reject。
进一步的，可选的，gNB将该NR的原因值发送给5GC的网元(例如AMF)，用于辅助5GC进行针对该终端的接入控制。
在具体实施过程中，上述图5、图6以及图7所示的实施例可以分别与图4所示的技术方案结合实施。例如，在图5所示的执行流程中，5GS NAS可以使用图4所示的方法来确定NR的原因值以及E-UTRA原因值。在图6所示的执行流程中，5GS NAS可以使用图4所示的方法来确定NAS的原因值，E-UTRA RRC层可以使用图4所示的方法来确定E-UTRA的原因值。另外，在图4所示的方法中，也可以将不同的方案结合实施。例如，5GS NAS可以仅根据AI或AC确定第一原因值，或者，5GS NAS也可以同时根据AI以及AC确定第一原因值。
图8为本申请提供的一种通信装置的实体框图。可选的，该通信装置可以是一种终端设备，也可以是终端设备中的一部分装置，例如终端设备中的芯片系统。可选的，该芯片系统，用于支持终端设备实现上述方法实施例中所涉及的功能，例如，生成，接收，发送，或处理上述方法中所涉及的数据和/或信息。可选的，该芯片系统还包括存储器，该存储器，用于保存终端设备必要的程序指令和数据。该芯片系统，包括芯片，也可以包括其他分立器件或电路结构。
如图8所示，该通信装置包括：
处理器801，处理器801用于与存储器802耦合，读取并执行存储器802中的指令，以实现：
确定建立RRC连接使用的第一无线接入技术。
根据接入信息确定建立上述RRC连接的第一原因值，该第一原因值是上述第一无线接入技术的原因值，该接入信息包括AI、AC以及第二无线接入技术的第二原因值之中的至少一种。
发送第一消息，该第一消息用于请求建立上述RRC连接，该第一消息中包括上述第一原因值。
进一步的，处理器801还用于：
根据上述第二原因值与上述第一原因值的映射关系，确定上述第一原因值。
进一步的，处理器801还用于：
根据上述AI与上述第一原因值的映射关系，确定上述第一原因值。
进一步的，处理器801还用于：
根据上述AC与上述第一原因值的映射关系，确定上述第一原因值。
进一步的，处理器801还用于：
由第一协议层根据上述接入信息，确定所述第一原因值。
进一步的，处理器801还用于：
由第二协议层从上述第一协议层获取上述第一原因值。
由第二协议层发送包含上述第一原因值的上述第一消息。
进一步的，处理器801还用于：
由第二协议层从上述第一协议层获取上述接入信息。
由第二协议层根据上述接入信息，确定上述第一原因值。
进一步的，上述第一无线接入技术包括E-UTRA技术，上述第二无线接入技术包括 NR技术。
进一步的，上述第一协议层为NAS，上述第二协议层为RRC层。
图9为本申请提供的通信装置的模块结构图，如图9所示，该装置包括：
处理模块901，用于确定建立RRC连接使用的第一无线接入技术；以及，
根据接入信息确定建立上述RRC连接的第一原因值，该第一原因值是上述第一无线接入技术的原因值，该接入信息包括AI、AC和第二无线接入技术的第二原因值中的至少一种。
发送模块902，用于发送第一消息，所述第一消息用于请求建立所述RRC连接，所述第一消息中包括所述第一原因值。
进一步的，处理模块901还用于：
根据上述第二原因值与上述第一原因值的映射关系，确定上述第一原因值。
进一步的，处理模块901还用于：
根据上述AI与上述第一原因值的映射关系，确定上述第一原因值。
进一步的，处理模块901还用于：
根据上述AC与上述第一原因值的映射关系，确定上述第一原因值。
进一步的，处理模块901还用于：
由第一协议层根据上述接入信息，确定所述第一原因值。
进一步的，处理模块901还用于：
由第二协议层从上述第一协议层获取上述第一原因值。
由第二协议层发送包含上述第一原因值的上述第一消息。
进一步的，处理模块901还用于：
由第二协议层从上述第一协议层获取上述接入信息。
由第二协议层根据上述接入信息，确定上述第一原因值。
进一步的，上述第一无线接入技术包括E-UTRA技术，上述第二无线接入技术包括NR技术。
进一步的，上述第一协议层为NAS，上述第二协议层为RRC层。
可选的，上述通信装置还可以包括收发器，用于支持上述通信装置执行上述方法实施例中收发数据、信令或信息，例如，发送第一消息。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导 体介质(例如固态硬盘Solid State Disk(SSD))等。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、装置(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (23)

  1. 一种通信方法，其特征在于，包括：
    终端确定建立无线资源控制RRC连接使用的第一无线接入技术；
    所述终端根据接入信息确定建立所述RRC连接的第一原因值，所述第一原因值是所述第一无线接入技术的原因值，所述接入信息包括接入标识AI、接入类别AC和第二无线接入技术的第二原因值中的至少一种；
    所述终端发送第一消息，所述第一消息用于请求建立所述RRC连接，所述第一消息中包括所述第一原因值。
  2. 根据权利要求1所述的方法，其特征在于，所述终端根据接入信息确定建立所述RRC连接的第一原因值，包括：
    所述终端根据所述第二原因值与所述第一原因值的映射关系，确定所述第一原因值。
  3. 根据权利要求1或2所述的方法，其特征在于，所述终端根据接入信息确定建立所述RRC连接的第一原因值，包括：
    所述终端根据所述AI与所述第一原因值的映射关系，确定所述第一原因值。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述终端根据接入信息确定建立所述RRC连接的第一原因值，包括：
    所述终端根据所述AC与所述第一原因值的映射关系，确定所述第一原因值。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述终端根据接入信息确定建立所述RRC连接的第一原因值，包括：
    所述终端的第一协议层根据所述接入信息，确定所述第一原因值。
  6. 根据权利要求5所述的方法，其特征在于，所述终端发送第一消息，包括：
    所述终端的第二协议层从所述第一协议层获取所述第一原因值；
    所述终端的第二协议层发送包含所述第一原因值的所述第一消息。
  7. 根据权利要求1-4任一项所述的方法，其特征在于，所述终端根据接入信息确定建立所述RRC连接的第一原因值，包括：
    所述终端的第二协议层从所述终端的第一协议层获取所述接入信息；
    所述终端的第二协议层根据所述接入信息，确定所述第一原因值。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述第一无线接入技术包括全球陆地无线接入E-UTRA技术，所述第二无线接入技术包括新空口NR技术。
  9. 根据权利要求5-8任一项所述的方法，其特征在于，所述第一协议层为非接入层NAS，所述第二协议层为RRC层。
  10. 根据权利要求2-4任一项所述的方法，其特征在于，所述映射关系可以预先通过以下任意一种方式配置：
    NAS信令消息配置、操作管理维护OAM配置、运营商预配置、默认配置。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述建立RRC连接包括新建RRC连接、恢复RRC连接或者重建RRC连接。
  12. 一种通信装置，其特征在于，包括处理器，所述处理器用于与存储器耦合，读取并执行所述存储器中的指令，以实现：
    确定建立无线资源控制RRC连接使用的第一无线接入技术；
    根据接入信息确定建立所述RRC连接的第一原因值，所述第一原因值是所述第一无线接入技术的原因值，所述接入信息包括接入标识AI、接入类别AC和第二无线接入技术的第二原因值中的至少一种；
    发送第一消息，所述第一消息用于请求建立所述RRC连接，所述第一消息中包括所述第一原因值。
  13. 根据权利要求12所述的装置，其特征在于，所述处理器还用于：
    根据所述第二原因值与所述第一原因值的映射关系，确定所述第一原因值。
  14. 根据权利要求12或13所述的装置，其特征在于，所述处理器还用于：
    根据所述AI与所述第一原因值的映射关系，确定所述第一原因值。
  15. 根据权利要求12-14任一项所述的装置，其特征在于，所述处理器还用于：
    根据所述AC与所述第一原因值的映射关系，确定所述第一原因值。
  16. 根据权利要求12-15任一项所述的装置，其特征在于，所述处理器还用于：
    第一协议层根据所述接入信息，确定所述第一原因值。
  17. 根据权利要求16所述的装置，其特征在于，所述处理器还用于：
    第二协议层从所述第一协议层获取所述第一原因值；
    第二协议层发送包含所述第一原因值的所述第一消息。
  18. 根据权利要求12-15任一项所述的装置，其特征在于，所述处理器还用于：
    第二协议层从所述第一协议层获取所述接入信息；
    第二协议层根据所述接入信息，确定所述第一原因值。
  19. 根据权利要求12-18任一项所述的装置，其特征在于，所述第一无线接入技术包括全球陆地无线接入E-UTRA技术，所述第二无线接入技术包括新空口NR技术。
  20. 根据权利要求16-19任一项所述的装置，其特征在于，所述第一协议层为非接入层NAS，所述第二协议层为RRC层。
  21. 根据权利要求13-15任一项所述的装置，其特征在于，所述映射关系可以预先通过以下任意一种方式配置：
    NAS信令消息配置、操作管理维护OAM配置、运营商预配置、默认配置。
  22. 根据权利要求12-21任一项所述的方法，其特征在于，所述建立RRC连接包括新建RRC连接、恢复RRC连接或者重建RRC连接。
  23. 一种可读存储介质，其特征在于，所述可读存储介质中存储有计算机程序，所述计算机程序用于实现权利要求1-11任一项所述的通信方法。
PCT/CN2019/086208 2018-05-11 2019-05-09 通信方法及装置 Ceased WO2019214683A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2020563718A JP7127153B2 (ja) 2018-05-11 2019-05-09 通信方法および通信装置
EP19799203.5A EP3793263B1 (en) 2018-05-11 2019-05-09 Communication method and apparatus
KR1020207034850A KR102435491B1 (ko) 2018-05-11 2019-05-09 통신 방법 및 장치
US17/094,266 US11425764B2 (en) 2018-05-11 2020-11-10 Communication method and communications apparatus for reporting establishment causes

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810451436.0A CN110475314B (zh) 2018-05-11 2018-05-11 通信方法及装置
CN201810451436.0 2018-05-11

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/094,266 Continuation US11425764B2 (en) 2018-05-11 2020-11-10 Communication method and communications apparatus for reporting establishment causes

Publications (1)

Publication Number Publication Date
WO2019214683A1 true WO2019214683A1 (zh) 2019-11-14

Family

ID=68467788

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/086208 Ceased WO2019214683A1 (zh) 2018-05-11 2019-05-09 通信方法及装置

Country Status (6)

Country Link
US (1) US11425764B2 (zh)
EP (1) EP3793263B1 (zh)
JP (1) JP7127153B2 (zh)
KR (1) KR102435491B1 (zh)
CN (2) CN110475314B (zh)
WO (1) WO2019214683A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110475314B (zh) * 2018-05-11 2021-02-26 华为技术有限公司 通信方法及装置
RU2763289C1 (ru) * 2018-07-02 2021-12-28 Нокиа Текнолоджиз Ой Управление доступом для оборудования пользователя в подсоединенном режиме
WO2021128110A1 (zh) * 2019-12-25 2021-07-01 华为技术有限公司 通信方法及装置
CN113556829B (zh) * 2020-04-23 2023-11-21 维沃移动通信有限公司 建立网络连接的方法和电子设备
CN114584998B (zh) * 2020-11-30 2024-03-22 中国移动通信有限公司研究院 无线资源控制实体的组件间的交互方法及设备
CN113891391B (zh) * 2021-09-14 2023-03-14 哲库科技(北京)有限公司 搜网方法、装置、终端设备及存储介质
US20230362624A1 (en) * 2022-05-04 2023-11-09 Apple Inc. User equipment aggregation

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107969015A (zh) * 2017-11-06 2018-04-27 江苏省邮电规划设计院有限责任公司 一种5g物联网电力数据采集终端接入控制方法

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101913259B1 (ko) * 2010-11-08 2018-10-30 엘지전자 주식회사 무선 통신 시스템에서 단말의 rrc 연결 방법 및 이를 위한 장치
CN104770016B (zh) * 2013-08-30 2019-03-08 华为技术有限公司 非接入层消息的处理方法、用户设备和网络侧设备
US9860834B2 (en) * 2013-09-13 2018-01-02 Lg Electronics Inc. Method for reselecting network node in charge of control plane
JP2018041996A (ja) * 2015-01-28 2018-03-15 シャープ株式会社 端末装置および方法
WO2016144009A1 (ko) * 2015-03-12 2016-09-15 엘지전자 주식회사 무선 통신 시스템에서 네트워크 트래픽을 제어하는 방법 및 단말
US10790879B2 (en) * 2016-03-28 2020-09-29 Huawei Technologies Co., Ltd. Method for routing data frame, near field communication controller, and terminal
CN109076437B (zh) * 2016-03-30 2021-11-30 Lg 电子株式会社 系统信息传输方法和基站、以及系统信息接收方法和用户设备
CN109005127B (zh) * 2017-02-03 2020-03-10 华为技术有限公司 一种QoS流处理方法、设备和通信系统
CN109246720B (zh) * 2017-05-11 2021-04-09 电信科学技术研究院 一种确定建立原因的方法和终端
CN111183665B (zh) * 2017-11-13 2023-04-28 上海朗帛通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
CN111587606B (zh) 2018-01-18 2023-09-08 瑞典爱立信有限公司 确定接入类别和/或建立原因的方法及相关装置
CN110475314B (zh) * 2018-05-11 2021-02-26 华为技术有限公司 通信方法及装置
EP4055897B1 (en) * 2019-11-07 2024-07-17 Ofinno, LLC Random access on multiple active protocol stacks

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107969015A (zh) * 2017-11-06 2018-04-27 江苏省邮电规划设计院有限责任公司 一种5g物联网电力数据采集终端接入控制方法

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Further Discussion on Slice Information over RRC", 3GPP TSG-RAN WG2 MEETING #101BIS, R2-1804616, 6 April 2018 (2018-04-06), XP051415603 *
HUAWEI ET AL.: "RRC Establishment Cause", 3GPP TSG-RAN WG2 MEETING #101BIS, R2-1805300, 5 April 2018 (2018-04-05), XP051415225 *
See also references of EP3793263A4 *

Also Published As

Publication number Publication date
EP3793263A1 (en) 2021-03-17
JP7127153B2 (ja) 2022-08-29
CN110475314A (zh) 2019-11-19
EP3793263A4 (en) 2021-07-14
CN113038574B (zh) 2022-05-24
US11425764B2 (en) 2022-08-23
KR102435491B1 (ko) 2022-08-24
US20210058986A1 (en) 2021-02-25
CN110475314B (zh) 2021-02-26
KR20210002717A (ko) 2021-01-08
EP3793263B1 (en) 2023-03-15
CN113038574A (zh) 2021-06-25
JP2021522754A (ja) 2021-08-30

Similar Documents

Publication Publication Date Title
CN109951824B (zh) 通信方法及装置
WO2019214683A1 (zh) 通信方法及装置
EP3739920B1 (en) Method, device, and system for configuring policy of ue
CN101166133B (zh) 家庭基站的位置限制方法及系统
EP3849242B1 (en) Method and apparatus for dynamically adjusting pdu session
EP3820192A1 (en) Communication method, access network device, and terminal device
CN113748697A (zh) 用于提供非接入层(nas)消息保护的方法和系统
CN111385830A (zh) 通信方法和装置
WO2019174444A1 (zh) 寻呼管理方法、网络数据分析功能及网络侧设备
WO2016177106A1 (zh) 专用核心网的选择方法和装置
KR20090077593A (ko) 메쉬 네트워크의 설정을 위한 능동 스캔 방법
WO2023045741A1 (zh) 定位方法及装置、可读存储介质
CN118433753A (zh) 经由双连接同时使用网络切片
EP3883270B1 (en) Method and apparatus for recognizing terminal
WO2021135188A1 (zh) 终端显示5g图标的方法、装置及计算机可读介质
CN108924883A (zh) 一种接入网络切片的方法和装置
CN111586735A (zh) 一种通信方法及装置
WO2023123218A1 (zh) 网络切片的请求方法、设备、存储介质及程序产品
WO2023065865A1 (zh) 一种通信方法及设备
WO2022153749A1 (ja) ユーザ機器、ネットワークノード及び基地局
CN104770007B (zh) 无线局域网的接入方法及装置
EP4654740A1 (en) Edge application server selection method and apparatus
US20250330795A1 (en) Communication method and communication apparatus
WO2025066165A1 (zh) 一种通信方法及装置
CN120456346A (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: 19799203

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020563718

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207034850

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019799203

Country of ref document: EP

Effective date: 20201211