WO2019029342A1 - 连接方法、配置更新方法、控制面设备和用户面设备 - Google Patents

连接方法、配置更新方法、控制面设备和用户面设备 Download PDF

Info

Publication number
WO2019029342A1
WO2019029342A1 PCT/CN2018/096513 CN2018096513W WO2019029342A1 WO 2019029342 A1 WO2019029342 A1 WO 2019029342A1 CN 2018096513 W CN2018096513 W CN 2018096513W WO 2019029342 A1 WO2019029342 A1 WO 2019029342A1
Authority
WO
WIPO (PCT)
Prior art keywords
plane device
information
user plane
connection
connection establishment
Prior art date
Application number
PCT/CN2018/096513
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 KR1020207003724A priority Critical patent/KR102244573B1/ko
Priority to EP22172636.7A priority patent/EP4120790B1/en
Priority to DK18844617.3T priority patent/DK3668255T3/da
Priority to EP18844617.3A priority patent/EP3668255B1/en
Priority to JP2020505362A priority patent/JP6944041B2/ja
Publication of WO2019029342A1 publication Critical patent/WO2019029342A1/zh
Priority to US16/741,503 priority patent/US11044599B2/en
Priority to US17/348,205 priority patent/US11540114B2/en

Links

Images

Classifications

    • 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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • 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
    • 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
    • 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/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices

Definitions

  • the present disclosure relates to the field of wireless communication technologies, but is not limited to the field of wireless communication technologies, and in particular, to a method for establishing a connection, a control plane device, and a user plane device.
  • the present disclosure provides a connection method, a configuration update method, a control plane device, and a user plane device.
  • connection method including:
  • the control plane device sends a first connection establishment request message to the user plane device, where the first connection establishment request message includes control plane device information;
  • the user plane device sends a first connection establishment success response message or a first connection establishment failure response message to the control plane device, where the first connection establishment success response message includes user plane device information, and the first connection failure response message includes a user plane.
  • the first connection establishment success response message includes user plane device information
  • the first connection failure response message includes a user plane.
  • connection method including:
  • the user plane device sends a second connection establishment request message to the control plane device, where the second connection establishment request message includes user plane device information;
  • the control plane device sends a second connection establishment success response message or a second connection establishment failure response message to the user plane device, where the second connection establishment success response message includes control plane device information, and the second connection failure response message includes a control plane Device information and connection establishment failure reasons.
  • the embodiment of the present disclosure further provides a configuration update method, including:
  • the user plane device sends a capability update message to the control plane device, where the capability update message includes user plane device information;
  • the control plane device sends a capability update confirmation message or a capability update failure message to the user plane device, where the capability update confirmation message includes control plane device information, and the capability update failure message includes control plane device information and a capability update failure reason.
  • control plane device includes a processor, a memory, and a communication bus;
  • the communication bus is configured to implement connection communication between the processor and the memory
  • the processor is configured to execute a connection program stored in the memory to implement the following steps:
  • the first connection establishment success response message includes user plane device information
  • the first connection failure response message includes user plane device information. And the reason for the connection establishment failure.
  • the embodiment of the present disclosure further provides a user plane device, where the user plane device includes a processor, a memory, and a communication bus;
  • the communication bus is configured to implement connection communication between the processor and the memory
  • the processor is configured to execute a connection program stored in the memory to implement the following steps:
  • the second connection establishment success response message includes control plane device information
  • the second connection failure response message includes control plane device information And the reason for the connection establishment failure.
  • the embodiment of the present disclosure further provides a user plane device, where the user plane device includes a processor, a memory, and a communication bus;
  • the communication bus is configured to implement connection communication between the processor and the memory
  • the processor is configured to execute a connection program stored in the memory to implement the following steps:
  • the capability update confirmation message includes control plane device information
  • the capability update failure message includes control plane device information and a capability update failure reason.
  • the embodiment of the present disclosure further provides a computer storage medium storing computer executable instructions; after the computer executable instructions are executed, the connection method provided by one or more of the foregoing technical solutions can be implemented or Configure the update method.
  • 1 is a schematic structural diagram of an interface between a first network element and a second network element in a 5G NR system
  • FIG. 2 is a schematic flow chart of a connection method according to some embodiments of the present disclosure.
  • FIG. 3 is a schematic flowchart diagram of a connection method according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart of a configuration update method according to some embodiments of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a control plane device according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of a user plane device according to some embodiments of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a user plane device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of an interface between a control plane device, a user plane device, and a second network element according to an example of the present disclosure
  • FIG. 9 is a schematic flowchart of a connection request initiated by a control plane device to establish a connection with a user plane device according to an example of the present disclosure
  • FIG. 10 is a schematic flowchart of a user plane device initiated connection request with a control plane device according to an example of the present disclosure
  • FIG. 11 is a schematic flowchart of a user plane device initiating a configuration update request according to an example of the present disclosure.
  • delay-insensitive network functions are placed in the first network element (for example, Centralized Unit (CU)) in consideration of non-ideal forward transmission.
  • the second network element for example, a distributed processing unit (DU) is transmitted between the first network element and the second network element through an ideal and/or non-ideal forward transmission network.
  • the control plane (CP) and user plane (UP) function sets in the existing first network element have been separated by a logical plane, they are physically integrated in a single network element. Therefore, based on the division of the first network element and the second network element, combined with the multiple considerations of transmission delay, load balancing, multi-vendor device interoperability, and deployment cost, the CP in the first network element is used. Further physical segmentation with UP enables CPs and UPs to be deployed in different geographical locations, independently configured, resource-expanded, and functionally upgraded, so that the requirements of various types of 5G services can be more flexibly and efficiently.
  • the CP entity can be deployed in the network center room, for example, in the CU entity, and manage multiple UP entities in the jurisdiction to efficiently coordinate the traffic load between multiple UP entities to achieve load balancing.
  • the CP entity is deployed at the edge of the network close to the DU entity according to requirements, which can greatly reduce the delay of the radio resource control (RRC) control plane signaling interaction, and fully satisfy the ultra-reliable low delay (Ultra-Reliable). And Low Latency Communications, URLLC) and other low latency services.
  • RRC radio resource control
  • Ultra-Reliable ultra-reliable low delay
  • URLLC Low Latency Communications
  • CP and UP separation can construct a more flexible and efficient network deployment method, which can further reduce the deployment cost while enhancing network performance.
  • the physical separation of CP-UP and the standardization of related interfaces greatly enhance the interoperability between CP and UP devices, making it possible for CP entities and UP entities to adopt devices of different vendors, and it is also beneficial for operators to further reduce the 5G foundation. The cost of purchasing a facility investment.
  • the CP entity includes RRC and Packet Data Convergence Protocol-Control (PDCP-C) processing layer for control plane signaling
  • the UP entity includes simple distributed file transmission system access.
  • SDAP Simple DFS Access Protocol
  • PDCP-U Packet Data Convergence Protocol-User
  • a many-to-many mapping connection mode can be adopted between the CP and the UP.
  • One CP can manage multiple UPs at the same time, and a resource provided by one UP can also be shared by multiple CPs.
  • the network element other than the system implements the establishment and configuration of the interface between the CP and the UP. On the one hand, it is not specified in the related technology. On the other hand, how to reduce the signaling overhead and delay as much as possible, and reduce the premature transmission caused by the large signaling overhead. The load of the interface.
  • OAM Operation Administration and Maintenance
  • the information is carried by the CP, for example, the CP carries its own control plane device information in the connection establishment request message, and the control
  • the device information may include: user plane device information established by the user to establish a connection between the CU and the UP, and may also include user plane device information not used for establishing the connection between the CU and the UP; thus, on the one hand, the user plane device information It can be used for connection establishment or not for connection establishment.
  • the CP knows the user plane device information of the UP, it can control the service data transmission of the UP plane.
  • the user plane control information may include: an UP name that may be used for establishing a connection between the CP and the UP, and may also include: a bearer attribute of the UP (for example, whether the UP supports the replication bearer capability information, and whether the bifurcation bearer capability is supported. The information, whether it supports the wireless packet data protocol capability, etc., so that the CP can subsequently carry out the bearer and/or transmission of the achievable service data for the UP according to these capabilities.
  • the connection establishment request message and the connection establishment response message (including the connection establishment failure response and the connection establishment success response), the capability update message or the capability update confirmation message or the capability update failure message, etc.
  • connection establishment used for the connection establishment message or In the capability update message, the control plane device information and the user plane device information are carried, and a message carries a plurality of information, and the connection establishment or capability update separately uses dedicated signaling, and uses a special letter, respectively, with respect to dedicated signaling.
  • the interaction control device information and the user plane device information are used to reduce the signaling overhead by signaling multiplexing, and the control plane device information and the user plane device that may be used later are completed in the process of establishing the connection. The interaction of information, so that when it is needed, no special request is required, and the delay of acquiring control plane device information and user plane device information is reduced.
  • a configuration update occurs in the CP or the UP, and the synchronization may be performed in the process of updating the configuration of the CU and the UP.
  • the capability update information is used to inform the other party of the updated control plane device information and the user plane device information in time to reduce subsequent use. Therefore, the solution provided by the present disclosure has a delay of use of small signaling overhead, control plane device information, and user plane device information.
  • connection method of the present disclosure may include the following steps:
  • Step 201 The control plane device sends a first connection establishment request message to the user plane device, where the first connection establishment request message includes control plane device information.
  • step 201 the method further includes:
  • the control plane device and the user plane device respectively obtain respective configuration information from the operation management and maintenance platform, the configuration information of the control plane device includes control plane device information; and the configuration information of the user plane device includes user plane device information. .
  • control plane device information includes any one of the following or any combination thereof:
  • Control surface device name (Identification, ID);
  • the control plane device is used to establish one or more Internet Protocol (IP) address information of the interface with the user plane device.
  • IP Internet Protocol
  • the user plane device information includes any one of the following or any combination thereof:
  • the user plane device is used to establish one or more IP address information of an interface with the control plane device.
  • Capability information of the user plane device is
  • the capability information of the user plane device includes any one of the following or any combination thereof:
  • the maximum number of user devices supported by the user plane device is the maximum number of user devices supported by the user plane device
  • the maximum number of distributed processing units supported by the user plane device is the maximum number of distributed processing units supported by the user plane device.
  • the bandwidth information of the user plane device includes data rate and band bandwidth information supported by the user plane device.
  • the capability information of the user plane device further includes any one of the following or any combination thereof:
  • Control plane device information connected to the user plane device
  • PLMN Public Land Mobile Network
  • Network slice configuration information supported by the user plane device
  • the version number information of the SDAP supported by the user plane device and the PDCP for the user plane data
  • the security processing capability information supported by the user plane device is the security processing capability information supported by the user plane device.
  • control plane device information of the user plane device connection includes any one of the following or any combination thereof: a control plane device list connected by the user plane device, and the user plane device and each control plane device Connection attribute information between.
  • the distributed processing unit information of the user plane device connection includes a distributed processing unit list of the user plane device connection and a connection attribute between the user plane device and each distributed processing unit. information.
  • connection attribute information includes any one of the following or any combination thereof:
  • the PLMN configuration information supported by the user plane device includes PLMN type information supported by the user plane device and resource quota information occupied by each PLMN type.
  • the slice configuration information supported by the user plane device includes slice type information supported by the user plane device and resource quota information occupied by each slice type.
  • the security processing capability information supported by the user plane device includes, but is not limited to, an encryption algorithm, an integrity protection algorithm, and header compression algorithm information supported by the user plane device.
  • the capability information of the user plane device further includes function information supported by the user plane device, and the function information includes any one of the following or any combination thereof:
  • RAT Radio Access Technology
  • Step 202 The user plane device sends a first connection establishment success response message or a first connection establishment failure response message to the control plane device, where the first connection establishment success response message includes user plane device information, the first connection failure response message. This includes user plane device information and the reason for the connection establishment failure.
  • connection method that can include the following steps:
  • Step 301 The user plane device sends a second connection establishment request message to the control plane device, where the second connection establishment request message includes user plane device information.
  • step 301 the method further includes:
  • the control plane device and the user plane device respectively obtain respective configuration information from the operation management and maintenance platform, the configuration information of the control plane device includes control plane device information; and the configuration information of the user plane device includes user plane device information. .
  • the content of the control plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the content of the user plane device information is the same as the foregoing step 201, and details are not described herein again.
  • Step 302 The control plane device sends a second connection establishment success response message or a second connection establishment failure response message to the user plane device, where the second connection establishment success response message includes control plane device information, and the second connection failure response message This includes control device information and the reason for the connection establishment failure.
  • a configuration update method of the present disclosure may include the following steps:
  • Step 401 The user plane device sends a capability update message to the control plane device, where the capability update message includes user plane device information.
  • step 401 the method further includes:
  • the control plane device and the user plane device respectively obtain respective configuration information from the operation management and maintenance platform, the configuration information of the control plane device includes control plane device information; and the configuration information of the user plane device includes user plane device information. ;
  • Establishing a connection between the control plane device and the user plane device (either by the control plane device initiating a connection request or by the user plane device to initiate a connection request).
  • the content of the control plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the content of the user plane device information is the same as the foregoing step 201, and details are not described herein again.
  • Step 402 The control plane device sends a capability update confirmation message or a capability update failure message to the user plane device, where the capability update confirmation message includes control plane device information, where the capability update failure message includes control plane device information and a capability update failure reason.
  • connection method including:
  • the control plane device sends a first connection establishment request message to the user plane device, where the first connection establishment request message includes control plane device information;
  • the control plane device receives a first connection establishment success response message or a first connection establishment failure response message from the user plane device, the first connection establishment success response message includes user plane device information, and the first connection failure response message includes the user The device information and the reason for the connection establishment failure.
  • the content of the control plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the content of the user plane device information is the same as the foregoing step 201, and details are not described herein again.
  • connection method including:
  • the user plane device sends a second connection establishment request message to the control plane device, where the second connection establishment request message includes user plane device information;
  • the user plane device receives a second connection establishment success response message or a second connection establishment failure response message from the control plane device, the second connection establishment success response message includes control plane device information, and the second connection failure response message includes control The device information and the reason for the connection establishment failure.
  • the content of the control plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the content of the user plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the embodiment of the present disclosure further provides a configuration update method, including:
  • the user plane device sends a capability update message to the control plane device, where the capability update message includes user plane device information;
  • the user plane device receives a capability update confirmation message or a capability update failure message from the control plane device, the capability update confirmation message includes control plane device information, and the capability update failure message includes control plane device information and a capability update failure reason.
  • the content of the control plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the content of the user plane device information is the same as the foregoing step 201, and details are not described herein again.
  • control plane device includes a processor, a memory, and a communication bus;
  • the communication bus is used to implement connection communication between a processor and a memory
  • the processor is configured to execute a connection program stored in the memory to implement the following steps:
  • the first connection establishment success response message includes user plane device information
  • the first connection failure response message includes user plane device information. And the reason for the connection establishment failure.
  • the content of the control plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the content of the user plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the embodiment of the present disclosure further provides a user plane device, where the user plane device includes a processor, a memory, and a communication bus;
  • the communication bus is used to implement connection communication between a processor and a memory
  • the processor is configured to execute a connection program stored in the memory to implement the following steps:
  • the second connection establishment success response message includes control plane device information
  • the second connection failure response message includes control plane device information And the reason for the connection establishment failure.
  • the content of the control plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the content of the user plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the embodiment of the present disclosure further provides a user plane device, where the user plane device includes a processor, a memory, and a communication bus;
  • the communication bus is configured to implement connection communication between the processor and the memory
  • the processor is configured to execute a connection program stored in the memory to implement the following steps:
  • the capability update confirmation message includes control plane device information
  • the capability update failure message includes control plane device information and a capability update failure reason.
  • the content of the control plane device information is the same as the foregoing step 201, and details are not described herein again.
  • the content of the user plane device information is the same as the foregoing step 201, and details are not described herein again.
  • an embodiment of the present disclosure further provides a control plane device, including a first sending unit 501 and a first receiving unit 502, where
  • the first sending unit 501 is configured to send a first connection establishment request message to the user plane device, where the first connection establishment request message includes control plane device information;
  • the first receiving unit 502 is configured to receive a first connection establishment success response message or a first connection establishment failure response message from the user plane device, where the first connection establishment success response message includes user plane device information, the first connection The failure response message includes user plane device information and a connection establishment failure reason.
  • the first receiving unit 502 is further configured to:
  • control plane device information includes any one of the following or any combination thereof:
  • the control plane device is configured to establish one or more IP address information for interfacing with the user plane device.
  • the user plane device information includes any one of the following or any combination thereof:
  • the user plane device is configured to establish one or more IP address information for interfacing with the control plane device.
  • Capability information of the user plane device is
  • the capability information of the user plane device includes any one of the following or any combination thereof:
  • the maximum number of user devices supported by the user plane device is the maximum number of user devices supported by the user plane device
  • the maximum number of distributed processing units supported by the user plane device is the maximum number of distributed processing units supported by the user plane device.
  • the bandwidth information of the user plane device includes data rate and band bandwidth information supported by the user plane device.
  • the capability information of the user plane device further includes any one of the following or any combination thereof:
  • Control surface device information connected to the user plane device
  • the version number information of the SDAP supported by the user plane device and the PDCP for the user plane data
  • the security processing capability information supported by the user plane device is the security processing capability information supported by the user plane device.
  • control plane device information of the user plane device connection includes at least one of the following: a control surface device list connected by the user plane device, and between the user face device and each control surface device Connection attribute information.
  • the distributed processing unit information of the user plane device connection includes a list of distributed processing units connected by the user plane device and connection attributes between the user plane device and each distributed processing unit. information.
  • connection attribute information includes any one of the following or any combination thereof:
  • the PLMN configuration information supported by the user plane device includes PLMN type information supported by the user plane device and resource quota information occupied by each PLMN type.
  • the slice configuration information supported by the user plane device includes slice type information supported by the user plane device and resource quota information occupied by each slice type.
  • the security processing capability information supported by the user plane device includes, but is not limited to, an encryption algorithm, an integrity protection algorithm, and header compression algorithm information supported by the user plane device.
  • the capability information of the user plane device further includes function information supported by the user plane device, and the function information includes any one of the following or any combination thereof:
  • an embodiment of the present disclosure further provides a user plane device, including a second sending unit 601 and a second receiving unit 602, where:
  • the second sending unit 601 is configured to send a second connection establishment request message to the control plane device, where the second connection establishment request message includes user plane device information;
  • the second receiving unit 602 is configured to receive a second connection establishment success response message or a second connection establishment failure response message from the control plane device, where the second connection establishment success response message includes control plane device information, the second connection The failure response message includes control plane device information and a connection establishment failure reason.
  • the second receiving unit 602 is further configured to:
  • the configuration information of the user plane device is obtained from the operation management and maintenance platform, and the configuration information of the user plane device includes user plane device information.
  • the content of the control plane device information is the same as that described above, and details are not described herein again.
  • the content of the user plane device information is the same as that described above, and details are not described herein again.
  • the present disclosure further provides a user plane device, including a third sending unit 701 and a third receiving unit 702, where:
  • the third sending unit 701 is configured to send a capability update message to the control plane device, where the capability update message includes user plane device information;
  • the third receiving unit 702 is configured to receive a capability update confirmation message or a capability update failure message from the control plane device, where the capability update confirmation message includes control plane device information, and the capability update failure message includes control plane device information and capability update. The reason for the failure.
  • the third sending unit 701 is further configured to send a second connection establishment request message to the control plane device, where the second connection establishment request message includes user plane device information;
  • the third receiving unit 702 is further configured to acquire configuration information of the user plane device from the operation management and maintenance platform, the configuration information of the user plane device includes user plane device information, and the second connection establishment success response of the receiving control plane device
  • the message or the second connection establishment failure response message, the second connection establishment success response message includes control plane device information
  • the second connection failure response message includes control plane device information and a connection establishment failure reason.
  • the content of the control plane device information is the same as that described above, and details are not described herein again.
  • the content of the user plane device information is the same as that described above, and details are not described herein again.
  • the present disclosure further provides a few examples to further explain the present disclosure, but it is noted that the examples are only for better description of the disclosure, and do not constitute a limitation to the disclosure.
  • the various embodiments below may exist independently, and the technical features in the different embodiments may be combined and used in combination in one embodiment.
  • the first connection establishment request message, the second connection establishment request message, the first connection establishment success response message, the first connection establishment failure response message, the second connection establishment success response message, the second connection establishment failure response message, and the capability The title of a message such as an update message, a capability update confirmation message, or a capability update failure message may change, and the title does not affect the method implementation in this article.
  • FIG. 8 is a schematic structural diagram of an interface between a control plane device CP of a first network element, a user plane device UP of a first network element, and a second network element.
  • the CP and the UP are respectively located in two different first network element CUs, and the separation of the user plane data and the control plane data is realized.
  • the interface between the CP device of the first network element and the second network element is an F1-C interface
  • the interface between the UP device of the first network element and the second network element is an F1-U interface.
  • the interface between the CP and the UP is the E1 interface.
  • FIG. 9 is a schematic flowchart of a CP initiated connection establishment request initiated by a CP according to the present disclosure.
  • the source CP sends a first connection establishment request message to the UP, and the message includes but is not limited to the following information:
  • the first connection establishes a successful response message:
  • the target UP After receiving the first connection establishment request message from the CP, the target UP sends a first connection establishment success response message to the CP, including but not limited to the following information:
  • the capability information of the UP includes but is not limited to the following cells:
  • connection attribute information between the target UP and each DU including but not limited to: delay, bandwidth, and the like;
  • the CP list to which the UP is connected and the connection attribute information between the target UP and each CP, including but not limited to: delay, bandwidth, and the like;
  • the PLMN related configuration information supported by the UP including but not limited to: type information of the PLMN and resource quota information occupied by each PLMN;
  • the slice-related configuration information supported by the UP including but not limited to: type information of the slice and resource quota information occupied by each slice;
  • the security processing capabilities supported by the UP including but not limited to encryption algorithms, integrity protection algorithms, and header compression algorithm information;
  • the target UP After receiving the first connection establishment request message from the CP, the target UP sends a first connection failure response message to the CP, including but not limited to the following information:
  • FIG. 10 is a schematic diagram of a UP initiated request to establish a connection with a CP according to the present disclosure.
  • Second connection establishment request message Direction: UP->CP
  • the source UP sends a second connection establishment request message to the CP, including but not limited to the following information:
  • the capability information of the UP includes but is not limited to the following cells:
  • the DU list and the connection attribute information between the source UP and each DU including but not limited to: delay, bandwidth, and the like;
  • the CP list and the connection attribute information between the source UP and each CP including but not limited to: delay, bandwidth, and the like;
  • the PLMN related configuration information supported by the UP including but not limited to: type information of the PLMN and resource quota information occupied by each PLMN;
  • the slice-related configuration information supported by the UP including but not limited to: type information of the slice and resource quota information occupied by each slice;
  • the security processing capabilities supported by the UP including but not limited to encryption algorithms, integrity protection algorithms, and header compression algorithm information;
  • the second connection establishes a successful response message:
  • the target CP After receiving the second connection establishment request message from the UP, the target CP sends a second connection establishment success response message to the UP, including but not limited to the following information:
  • the second connection establishment failure response message Direction: CP->UP
  • the target CP After receiving the second connection establishment request message from the UP, the target CP sends a second connection establishment failure response message to the UP, including but not limited to the following information:
  • FIG. 11 is a schematic diagram of a process for implementing an UP configuration update between a CP and an UP provided by the present disclosure.
  • the source UP sends a capability update message to all CPs in the CP list that is currently connected to the source UP, including but not limited to the following information:
  • the capability information of the source UP update includes but is not limited to the following cells:
  • the DU list to which the source UP is connected and the connection attribute information between the source UP and each DU, including but not limited to: delay, bandwidth, and the like;
  • the CP list to which the source UP is connected and the connection attribute information between the source UP and each CP, including but not limited to: delay, bandwidth, and the like;
  • PLMN related configuration information supported by the source UP including but not limited to: type information of the PLMN and resource quota information occupied by each PLMN;
  • the slice-related configuration information supported by the source UP including but not limited to: type information of the slice and resource quota information occupied by each slice;
  • the target CP After receiving the capability update message from the UP, the target CP sends a capability update confirmation message to the UP, including but not limited to the following information:
  • the target CP After receiving the capability update message from the UP, the target CP sends a capability update failure message to the UP, including but not limited to the following information:
  • the embodiment of the present disclosure further provides a computer storage medium storing computer executable instructions; after the computer executable instructions are executed, the connection method provided by one or more of the foregoing technical solutions can be implemented or Configure the update method.
  • the computer storage medium provided by this embodiment may be various types of storage media, such as a read-only storage medium, a flash memory, a random storage medium, or the like.
  • the computer storage medium can include a non-transitory storage medium.

Abstract

本公开提供了一种连接方法、配置更新方法、控制面设备和用户面设备，包括控制面设备向用户面设备发送第一建立连接请求消息，所述第一建立连接请求消息包括控制面设备信息；用户面设备向控制面设备发送第一连接建立成功响应消息或第一连接建立失败响应消息，所述第一连接建立成功响应消息包括用户面设备信息，所述第一连接失败响应消息包括用户面设备信息及连接建立失败原因。本公开还提供了一种计算机存储介质。

Description

连接方法、配置更新方法、控制面设备和用户面设备
相关申请的交叉引用
本公开基于申请号为201710682460.0、申请日为2017年08月10日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本公开作为参考。
技术领域
本公开涉及无线通信技术领域但不限于无线通信技术领域，尤其涉及一种建立连接的方法、控制面设备和用户面设备。
背景技术
随着5G移动通信时代的到来，海量连接以及更高的数据传输速率要求对长期演进(Long Term Evolution，LTE)系统中室内基带处理单元(Building Baseband Unit，BBU)与远端射频模块(Remote Radio Unit，RRU)之间的前传(Front haul)网络接口——通用公共无线电接口(Common Public Radio Interface，CPRI)的传输容量提出了极大挑战。由于CPRI接口传输的是经过物理层编码调制等处理后的同相/正交(In-phase/Quadrature，IQ)信号，对应的数字比特流速率巨大，因此CPRI接口对传输时延和带宽都有较大的要求。当5G空口速率提升到数十吉比特每秒(Gbps)后，CPRI接口的传输流量需求将至少上升到太比特每秒(Tbps)级别，这对前传网络接口的部署成本和难度都带来了巨大的压力。
发明内容
本公开提供了一种连接方法、配置更新方法、控制面设备和用户面设 备。
本公开实施例的技术方案是这样实现的：
本公开实施例提供了一种连接方法，包括：
控制面设备向用户面设备发送第一建立连接请求消息，所述第一建立连接请求消息包括控制面设备信息；
用户面设备向控制面设备发送第一连接建立成功响应消息或第一连接建立失败响应消息，所述第一连接建立成功响应消息包括用户面设备信息，所述第一连接失败响应消息包括用户面设备信息及连接建立失败原因。
本公开实施例还提供了一种连接方法，包括：
用户面设备向控制面设备发送第二建立连接请求消息，所述第二建立连接请求消息包括用户面设备信息；
控制面设备向用户面设备发送第二连接建立成功响应消息或第二连接建立失败响应消息，所述第二连接建立成功响应消息包括控制面设备信息，所述第二连接失败响应消息包括控制面设备信息及连接建立失败原因。
本公开实施例还提供了一种配置更新方法，包括：
用户面设备向控制面设备发送能力更新消息，所述能力更新消息包括用户面设备信息；
控制面设备向用户面设备发送能力更新确认消息或能力更新失败消息，所述能力更新确认消息包括控制面设备信息，所述能力更新失败消息包括控制面设备信息及能力更新失败原因。
本公开实施例还提供了一种控制面设备，所述控制面设备包括处理器、存储器及通信总线；
所述通信总线配置为实现处理器和存储器之间的连接通信；
所述处理器配置为执行存储器中存储的连接程序，以实现以下步骤：
向用户面设备发送第一建立连接请求消息，所述第一建立连接请求消 息包括控制面设备信息；
接收来自用户面设备的第一连接建立成功响应消息或第一连接建立失败响应消息，所述第一连接建立成功响应消息包括用户面设备信息，所述第一连接失败响应消息包括用户面设备信息及连接建立失败原因。
本公开实施例还提供了一种用户面设备，所述用户面设备包括处理器、存储器及通信总线；
所述通信总线配置为实现处理器和存储器之间的连接通信；
所述处理器配置为执行存储器中存储的连接程序，以实现以下步骤：
向控制面设备发送第二建立连接请求消息，所述第二建立连接请求消息包括用户面设备信息；
接收来自控制面设备的第二连接建立成功响应消息或第二连接建立失败响应消息，所述第二连接建立成功响应消息包括控制面设备信息，所述第二连接失败响应消息包括控制面设备信息及连接建立失败原因。
本公开实施例还提供了一种用户面设备，所述用户面设备包括处理器、存储器及通信总线；
所述通信总线配置为实现处理器和存储器之间的连接通信；
所述处理器配置为执行存储器中存储的连接程序，以实现以下步骤：
向控制面设备发送能力更新消息，所述能力更新消息包括用户面设备信息；
接收来自控制面设备的能力更新确认消息或能力更新失败消息，所述能力更新确认消息包括控制面设备信息，所述能力更新失败消息包括控制面设备信息及能力更新失败原因。
本公开实施例还提供了一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令；所述计算机可执行指令被执行后，能够实现前述的一个或多个技术方案提供的连接方法或配置更新方法。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本公开的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1为5G NR系统中第一网元和第二网元之间的接口结构示意图；
图2为本公开一些实施例的一种连接方法的流程示意图；
图3为本公开实施例的一种连接方法的流程示意图；
图4为本公开一些实施例的一种配置更新方法的流程示意图；
图5为本公开实施例的一种控制面设备的结构示意图；
图6为本公开一些实施例的一种用户面设备的结构示意图；
图7为本公开实施例的一种用户面设备的结构示意图；
图8为本公开示例的一种控制面设备、用户面设备与第二网元之间的接口结构示意图；
图9为本公开示例的一种控制面设备发起的与用户面设备建立连接请求的流程示意图；
图10为本公开示例的一种用户面设备发起的与控制面设备建立连接请求的流程示意图；
图11为本公开示例的一种用户面设备发起配置更新请求的流程示意图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚明白，下文中将结合附图对本公开的实施例进行详细说明。需要说明的是，在不冲突的情况下，本公开中的实施例及实施例中的特征可以相互任意组合。
在5G新无线(New Radio，NR)系统中，需要从传输容量、传输时延、方便部署等几方面综合考虑，重新定义前传网络接口的划分方式。如图1 所示，考虑到非理想前传传输，将时延不敏感的网络功能放在第一网元(例如，集中式处理单元(Centralized Unit，CU))中，将时延敏感的网络功能放在第二网元(例如，分布式处理单元(Distributed Unit，DU))中，第一网元与第二网元之间通过理想和/或非理想的前传网络进行传输。
不同服务质量(Quality of Service，QoS)要求的5G用户业务和不均衡的用户业务物理分布，对5G网络的组网部署和数据传输性能的需求不同，这些不同类型的数据业务往往交织并存，或者在局部区域热点爆发，使得目前相对封闭的网络架构，不能高效地支撑各类5G通讯场景。虽然现有第一网元中的控制面(Control plane，CP)和用户面(User plane，UP)功能集已经被逻辑层面分割，但是物理上还是集成在单个网元内。因此，在第一网元和第二网元划分的基础上，结合传输时延、负载均衡、多厂商设备互操作性以及部署成本等多个角度的综合考虑，对第一网元中的CP和UP进行进一步的物理分割，使得CP和UP可以部署在不同的地理位置、独立地被配置、资源扩展和功能升级，从而可以更加灵活高效地满足各类5G业务的需求。
从部署位置看，既可以将CP实体部署在网络中心机房，例如CU实体内，同时管理辖区内多个UP实体，高效协调多个UP实体之间的业务负载，达到负载均衡的目的；也可以根据需求将CP实体部署在网络边缘靠近DU实体的位置，这样可以大大减小无线资源控制(Radio Resource Control，RRC)控制面信令交互的时延，充分满足超可靠低时延(Ultra-Reliable and Low Latency Communications，URLLC)等低延时业务的需求。
从运营商角度看，CP和UP分离可以构造更加灵活和高效的网络部署方式，在增强网络性能的同时，可以进一步降低部署成本。同时CP-UP物理分离及相关接口的标准化，极大增强了CP和UP设备之间的互操作性，使得CP实体和UP实体采用不同厂商的设备成为可能，也有利于运营商进一 步降低5G基础设施投资购买的成本。
从空口用户面划分的角度看，CP实体包含RRC和用于控制面信令的分组数据汇聚协议(Packet Data Convergence Protocol-Control，PDCP-C)处理层，UP实体包含简单分布式文件传输系统访问协议(Simple DFS Access Protocol，SDAP)和用于用户面数据的分组数据汇聚协议(Packet Data Convergence Protocol-User，PDCP-U)处理层。CP和UP之间可以采用多对多的映射连接方式，一个CP可以同时管理多个UP，而一个UP提供的资源也可以由多个CP共享。由于CP和UP之间存在多对多的连接关系，如何实现CP与UP之间接口的建立及配置更新，例如，是借助操作管理维护(Operation Administration and Maintenance，OAM)平台，还是借助操作管理维护系统以外的网元实现CP与UP之间接口的建立和配置，一方面在相关技术中没有规定，另一方面如何尽可能的减少信令开销及时延，并减少因为信令开销大导致的前传接口的负荷。有鉴于此，在本公开实施例中，在互相分离的CP和UP建立连接的过程中，会携带自身的信息，例如，CP会在连接建立请求消息中携带自身的控制面设备信息，该控制面设备信息可包括：用户连CU和UP之间连接建立的用户面设备信息，也可以包括不用于CU和UP之间本次连接建立的用户面设备信息；如此，一方面该用户面设备信息可用于连接建立，也可以不用于连接建立，但是CP知道了UP的用户面设备信息之后，可以控制UP面的业务数据传输。例如，所述用户面控制信息可包括：可以用于CP和UP之间连接建立的UP名称，也可包括：UP的承载属性(例如，UP是否支持复制承载能力信息，是否支持分叉承载能力信息，是否支持无线分组数据协议能力)等，如此，CP后续可以根据这些能力，为UP选择其可实现的业务数据进行承载和/或传输。如此，在连接建立使用的连接建立请求消息及连接建立响应消息(包含连接建立失败响应和连接建立成功响应)、能力更新消息或能力更新确认消息或能力更 新失败消息等用于连接建立的消息或能力更新的消息中，来承载控制面设备信息和用户面设备信息，实现了一个消息承载多种信息，相对于专用的信令分别传输连接建立或能力更新过使用专用信令、并用专门的信令来交互控制面设备信息和用户面设备信息，通过信令的复用，减少了信令的开销，在连接建立的过程中就完成了后续可能会使用到的控制面设备信息和用户面设备信息的交互，如此在需要使用时，不用专门请求，减少了获取控制面设备信息和用户面设备信息的时延。另外CP或UP发生了配置更新，可能会同步使得CU和UP的配置更新的过程中，通过能力更新信息及时的告知对方更新后的控制面设备信息和用户面设备信息，以减少后续的使用时延，故本公开提供的方案，具有信令开销小、控制面设备信息和用户面设备信息的使用延时。
如图2所示，本公开的一种连接方法可包括如下步骤：
步骤201：控制面设备向用户面设备发送第一建立连接请求消息，所述第一建立连接请求消息包括控制面设备信息；
需要说明的是，在步骤201之前，所述方法还包括：
所述控制面设备与所述用户面设备分别从操作管理维护平台获取各自的配置信息，所述控制面设备的配置信息包括控制面设备信息；所述用户面设备的配置信息包括用户面设备信息。
在一些实施例中，所述控制面设备信息包括以下任意一项或其任意组合：
控制面设备名称(Identification，ID)；
控制面设备用于建立与用户面设备的接口的1个或多个网际协议(Internet Protocol，IP)地址信息。
在一些实施例中，所述用户面设备信息包括以下任意一项或其任意组合：
用户面设备ID；
用户面设备用于建立与控制面设备的接口的1个或多个IP地址信息。
用户面设备的能力信息。
在一些实施例中，所述用户面设备的能力信息包括以下任意一项或其任意组合：
所述用户面设备的带宽信息；
所述用户面设备支持的最大用户设备数目；
所述用户面设备支持的最大分布式处理单元数目。
在本公开一些实施例中，所述用户面设备的带宽信息包括所述用户面设备支持的数据速率及频段带宽信息。
在一些实施例中，所述用户面设备的能力信息还包括以下任意一项或其任意组合：
所述用户面设备连接的分布式处理单元信息；
所述用户面设备连接的控制面设备信息；
所述用户面设备支持的公共陆地移动网络(Public Land Mobile Network，PLMN)配置信息；
所述用户面设备支持的网络切片(Slice)配置信息；
所述用户面设备支持的SDAP和用于用户面数据的PDCP的版本号信息；
所述用户面设备支持的安全处理能力信息。
在本公开一些实施例中，所述用户面设备连接的控制面设备信息包括以下任意一项或其任意组合：用户面设备连接的控制面设备列表，所述用户面设备与各个控制面设备之间的连接属性信息。
在本公开一些实施例中，所述用户面设备连接的分布式处理单元信息包括所述用户面设备连接的分布式处理单元列表以及所述用户面设备与各个分布式处理单元之间的连接属性信息。
在一些实施例中，所述连接属性信息包括以下任意一项或其任意组合：
连接的带宽；
支持的速率；
连接延迟。
在本公开一些实施例中，所述用户面设备支持的PLMN配置信息包括所述用户面设备支持的PLMN类型信息及各PLMN类型所占的资源配额信息。
在本公开一些实施例中，所述用户面设备支持的Slice配置信息包括用户面设备支持的Slice类型信息及各Slice类型所占的资源配额信息。
在一些实施例中，所述用户面设备支持的安全处理能力信息包括但不限于所述用户面设备支持的加密算法、完整性保护算法及头压缩算法信息。
所述用户面设备的能力信息还包括所述用户面设备支持的功能信息，所述功能信息包括以下任意一项或其任意组合：
是否支持复制承载(Duplication Bearer)信息；
是否支持分叉承载(Split Bearer)信息；
是否支持辅小区(Secondary Cell Group，SCG)分叉承载(Split Bearer)信息；
支持的无线接入技术(Radio Access Technology，RAT)类型信息；
是否支持NR PDCP信息；
是否支持巨型帧(jumbo frame)信息。
步骤202：用户面设备向控制面设备发送第一连接建立成功响应消息或第一连接建立失败响应消息，所述第一连接建立成功响应消息包括用户面设备信息，所述第一连接失败响应消息包括用户面设备信息及连接建立失败原因。
如图3所示，本公开提供一种连接方法可包括如下步骤：
步骤301：用户面设备向控制面设备发送第二建立连接请求消息，所述 第二建立连接请求消息包括用户面设备信息；
需要说明的是，在步骤301之前，所述方法还包括：
所述控制面设备与所述用户面设备分别从操作管理维护平台获取各自的配置信息，所述控制面设备的配置信息包括控制面设备信息；所述用户面设备的配置信息包括用户面设备信息。
在一些实施例中，所述控制面设备信息的内容同前文的步骤201所述，此处不再赘述。
在一些实施例中，所述用户面设备信息的内容同前文的步骤201所述，此处不再赘述。
步骤302：控制面设备向用户面设备发送第二连接建立成功响应消息或第二连接建立失败响应消息，所述第二连接建立成功响应消息包括控制面设备信息，所述第二连接失败响应消息包括控制面设备信息及连接建立失败原因。
如图4所示，本公开的一种配置更新方法可包括如下步骤：
步骤401：用户面设备向控制面设备发送能力更新消息，所述能力更新消息包括用户面设备信息；
需要说明的是，在步骤401之前，所述方法还包括：
所述控制面设备与所述用户面设备分别从操作管理维护平台获取各自的配置信息，所述控制面设备的配置信息包括控制面设备信息；所述用户面设备的配置信息包括用户面设备信息；
所述控制面设备与所述用户面设备之间建立连接(由控制面设备发起建立连接请求或者由用户面设备发起建立连接请求均可)。
在一些实施例中，所述控制面设备信息的内容同前文的步骤201所述，此处不再赘述。
在一些实施例中，所述用户面设备信息的内容同前文的步骤201所述， 此处不再赘述。
步骤402：控制面设备向用户面设备发送能力更新确认消息或能力更新失败消息，所述能力更新确认消息包括控制面设备信息，所述能力更新失败消息包括控制面设备信息及能力更新失败原因。
本公开实施例还提供了一种连接方法，包括：
控制面设备向用户面设备发送第一建立连接请求消息，所述第一建立连接请求消息包括控制面设备信息；
控制面设备接收来自用户面设备的第一连接建立成功响应消息或第一连接建立失败响应消息，所述第一连接建立成功响应消息包括用户面设备信息，所述第一连接失败响应消息包括用户面设备信息及连接建立失败原因。
在一些实施例中，所述控制面设备信息的内容同前文的步骤201所述，此处不再赘述。
在一些实施例中，所述用户面设备信息的内容同前文的步骤201所述，此处不再赘述。
本公开实施例还提供了一种连接方法，包括：
用户面设备向控制面设备发送第二建立连接请求消息，所述第二建立连接请求消息包括用户面设备信息；
用户面设备接收来自控制面设备的第二连接建立成功响应消息或第二连接建立失败响应消息，所述第二连接建立成功响应消息包括控制面设备信息，所述第二连接失败响应消息包括控制面设备信息及连接建立失败原因。
在一些实施例中，所述控制面设备信息的内容同前文的步骤201所述，此处不再赘述。
在一些实施例中，所述用户面设备信息的内容同前文的步骤201所述， 此处不再赘述。
本公开实施例还提供了一种配置更新方法，包括：
用户面设备向控制面设备发送能力更新消息，所述能力更新消息包括用户面设备信息；
用户面设备接收来自控制面设备的能力更新确认消息或能力更新失败消息，所述能力更新确认消息包括控制面设备信息，所述能力更新失败消息包括控制面设备信息及能力更新失败原因。
在一些实施例中，所述控制面设备信息的内容同前文的步骤201所述，此处不再赘述。
在一些实施例中，所述用户面设备信息的内容同前文的步骤201所述，此处不再赘述。
本公开实施例还提供了一种控制面设备，所述控制面设备包括处理器、存储器及通信总线；
所述通信总线用于实现处理器和存储器之间的连接通信；
所述处理器用于执行存储器中存储的连接程序，以实现以下步骤：
向用户面设备发送第一建立连接请求消息，所述第一建立连接请求消息包括控制面设备信息；
接收来自用户面设备的第一连接建立成功响应消息或第一连接建立失败响应消息，所述第一连接建立成功响应消息包括用户面设备信息，所述第一连接失败响应消息包括用户面设备信息及连接建立失败原因。
在一些实施例中，所述控制面设备信息的内容同前文的步骤201所述，此处不再赘述。
在一些实施例中，所述用户面设备信息的内容同前文的步骤201所述，此处不再赘述。
本公开实施例还提供了一种用户面设备，所述用户面设备包括处理器、 存储器及通信总线；
所述通信总线用于实现处理器和存储器之间的连接通信；
所述处理器用于执行存储器中存储的连接程序，以实现以下步骤：
向控制面设备发送第二建立连接请求消息，所述第二建立连接请求消息包括用户面设备信息；
接收来自控制面设备的第二连接建立成功响应消息或第二连接建立失败响应消息，所述第二连接建立成功响应消息包括控制面设备信息，所述第二连接失败响应消息包括控制面设备信息及连接建立失败原因。
在一些实施例中，所述控制面设备信息的内容同前文的步骤201所述，此处不再赘述。
在一些实施例中，所述用户面设备信息的内容同前文的步骤201所述，此处不再赘述。
本公开实施例还提供了一种用户面设备，所述用户面设备包括处理器、存储器及通信总线；
所述通信总线配置为实现处理器和存储器之间的连接通信；
所述处理器配置为执行存储器中存储的连接程序，以实现以下步骤：
向控制面设备发送能力更新消息，所述能力更新消息包括用户面设备信息；
接收来自控制面设备的能力更新确认消息或能力更新失败消息，所述能力更新确认消息包括控制面设备信息，所述能力更新失败消息包括控制面设备信息及能力更新失败原因。
在一些实施例中，所述控制面设备信息的内容同前文的步骤201所述，此处不再赘述。
在一些实施例中，所述用户面设备信息的内容同前文的步骤201所述，此处不再赘述。
如图5所示，本公开实施例还提供了一种控制面装置，包括第一发送单元501和第一接收单元502，其中，
第一发送单元501，配置为向用户面装置发送第一建立连接请求消息，所述第一建立连接请求消息包括控制面装置信息；
第一接收单元502，配置为接收来自用户面装置的第一连接建立成功响应消息或第一连接建立失败响应消息，所述第一连接建立成功响应消息包括用户面装置信息，所述第一连接失败响应消息包括用户面装置信息及连接建立失败原因。
在一些实施例中，所述第一接收单元502还配置为：
从操作管理维护平台获取所述控制面装置的配置信息，所述控制面装置的配置信息包括所述控制面装置信息。
在一些实施例中，所述控制面装置信息包括以下任意一项或其任意组合：
控制面装置ID；
控制面装置用于建立与用户面装置的接口的1个或多个IP地址信息。
在一些实施例中，所述用户面装置信息包括以下任意一项或其任意组合：
用户面装置ID；
用户面装置配置为建立与控制面装置的接口的1个或多个IP地址信息。
用户面装置的能力信息。
在一些实施例中，所述用户面装置的能力信息包括以下任意一项或其任意组合：
所述用户面装置的带宽信息；
所述用户面装置支持的最大用户设备数目；
所述用户面装置支持的最大分布式处理单元数目。
在本公开一些实施例中，所述用户面装置的带宽信息包括所述用户面装置支持的数据速率及频段带宽信息。
在一些实施例中，所述用户面装置的能力信息还包括以下任意一项或其任意组合：
所述用户面装置连接的分布式处理单元信息；
所述用户面装置连接的控制面装置信息；
所述用户面装置支持的PLMN配置信息；
所述用户面装置支持的Slice配置信息；
所述用户面装置支持的SDAP和用于用户面数据的PDCP的版本号信息；
所述用户面装置支持的安全处理能力信息。
在本公开一些实施例中，所述用户面装置连接的控制面装置信息包括所述以下至少之一：用户面装置连接的控制面装置列表，所述用户面装置与各个控制面装置之间的连接属性信息。
在本公开一些实施例中，所述用户面装置连接的分布式处理单元信息包括所述用户面装置连接的分布式处理单元列表以及所述用户面装置与各个分布式处理单元之间的连接属性信息。
在一些实施例中，所述连接属性信息包括以下任意一项或其任意组合：
连接的带宽；
支持的速率；
连接延迟。
在本公开一些实施例中，所述用户面装置支持的PLMN配置信息包括所述用户面装置支持的PLMN类型信息及各PLMN类型所占的资源配额信息。
在本公开一些实施例中，所述用户面装置支持的Slice配置信息包括用户面装置支持的Slice类型信息及各Slice类型所占的资源配额信息。
在一些实施例中，所述用户面装置支持的安全处理能力信息包括但不限于所述用户面装置支持的加密算法、完整性保护算法及头压缩算法信息。
在一些实施例中，所述用户面装置的能力信息还包括所述用户面装置支持的功能信息，所述功能信息包括以下任意一项或其任意组合：
是否支持Duplication Bearer信息；
是否支持Split Bearer信息；
是否支持SCG Split Bearer信息；
支持的RAT类型信息；
是否支持NR PDCP信息；
是否支持Jumbo Frame信息。
如图6所示，本公开实施例还提供了一种用户面装置，包括第二发送单元601和第二接收单元602，其中：
第二发送单元601，配置为向控制面装置发送第二建立连接请求消息，所述第二建立连接请求消息包括用户面装置信息；
第二接收单元602，配置为接收来自控制面装置的第二连接建立成功响应消息或第二连接建立失败响应消息，所述第二连接建立成功响应消息包括控制面装置信息，所述第二连接失败响应消息包括控制面装置信息及连接建立失败原因。
需要说明的是，第二接收单元602还配置为：
从操作管理维护平台获取所述用户面装置的配置信息，所述用户面装置的配置信息包括用户面装置信息。
在一些实施例中，所述控制面装置信息的内容同前文所述，此处不再赘述。
在一些实施例中，所述用户面装置信息的内容同前文所述，此处不再赘述。
如图7所示，本公开还提供了一种用户面装置，包括第三发送单元701和第三接收单元702，其中：
第三发送单元701，配置为向控制面装置发送能力更新消息，所述能力更新消息包括用户面装置信息；
第三接收单元702，配置为接收来自控制面装置的能力更新确认消息或能力更新失败消息，所述能力更新确认消息包括控制面装置信息，所述能力更新失败消息包括控制面装置信息及能力更新失败原因。
需要说明的是，所述第三发送单元701还配置为，向控制面装置发送第二建立连接请求消息，所述第二建立连接请求消息包括用户面装置信息；
所述第三接收单元702还配置为从操作管理维护平台获取所述用户面装置的配置信息，所述用户面装置的配置信息包括用户面装置信息；接收控制面装置的第二连接建立成功响应消息或第二连接建立失败响应消息，所述第二连接建立成功响应消息包括控制面装置信息，所述第二连接失败响应消息包括控制面装置信息及连接建立失败原因。
在一些实施例中，所述控制面装置信息的内容同前文所述，此处不再赘述。
在一些实施例中，所述用户面装置信息的内容同前文所述，此处不再赘述。
本公开实施例还提供了几个示例对本公开进行进一步解释，但是值得注意的是，该示例只是为了更好的描述本公开，并不构成对本公开不当的限定。下面的各个实施例可以独立存在，且不同实施例中的技术特点可以组合在一个实施例中联合使用。本文中的第一建立连接请求消息、第二建立连接请求消息、第一连接建立成功响应消息、第一连接建立失败响应消息、第二连接建立成功响应消息、第二连接建立失败响应消息、能力更新消息、能力更新确认消息或能力更新失败消息等消息的称谓可以发生变化， 称谓不影响本文中的方法实施。
图8为第一网元的控制面设备CP、第一网元的用户面设备UP及第二网元之间的接口结构示意图。CP和UP分别位于两个不同的第一网元CU内，实现了用户面数据与控制面数据的分离。为了方便描述，我们称第一网元的CP设备与第二网元之间的接口为F1-C接口，第一网元的UP设备与第二网元之间的接口为F1-U接口，CP和UP之间接口为E1接口。
示例1
图9为本公开提供的CP发起的与UP建立连接请求流程示意图。
第一建立连接请求消息：方向：CP->UP
源CP向UP发送第一建立连接请求消息，该消息包括但不限于以下信息：
-源CP的标识信息。
第一连接建立成功响应消息：方向：UP->CP
目标UP收到来自CP的第一建立连接请求消息后，向CP发送第一连接建立成功响应消息，该消息包括但不限于以下信息：
-目标UP的标识信息。
-目标UP的能力信息。
其中该UP的能力信息包括但不限于以下信元：
-该UP的带宽信息；
-该UP所支持的最大UE数目；
-该UP所支持的最大DU数目；
-该UP所连接的DU list以及目标UP与各个DU之间的连接属性信息，包括但不限于：时延、带宽等信息；
-该UP所连接的CP list以及目标UP与各个CP之间的连接属性信息，包括但不限于：时延、带宽等信息；
-该UP所支持的PLMN相关配置信息，包含但不限于：PLMN的类型信息及各PLMN所占的资源配额信息；
-该UP所支持的Slice相关配置信息，包含但不限于：Slice的类型信息及各Slice所占的资源配额信息；
-该UP所支持的SDAP和PDCP-U的版本号信息；
-该UP所支持的安全处理能力，包括但不限于加密算法、完整性保护算法及头压缩算法信息；
-对其他可选功能的支持信息，包括但不限于：是否支持duplication bearer等。
第一连接建立失败响应消息：方向：UP->CP
目标UP收到来自CP的第一建立连接请求消息后，向CP发送第一连接失败响应消息，该消息包括但不限于以下信息：
-目标UP的IP地址信息；
-失败原因。
示例2
图10为本公开提供的UP发起的与CP建立连接请求流程示意图。
第二建立连接请求消息：方向：UP->CP
源UP向CP发送第二建立连接请求消息，该消息包括但不限于以下信息：
-源UP的标识信息；
-源UP的能力信息；
其中，该UP的能力信息包括但不限于以下信元：
-该UP的带宽信息；
-该UP所支持的最大UE数目；
-该UP所支持的最大DU数目；
-该UP所连接的DU list以及源UP与各个DU之间的连接属性信息，包括但不限于：时延、带宽等信息；
-该UP所连接的CP list以及源UP与各个CP之间的连接属性信息，包括但不限于：时延、带宽等信息；
-该UP所支持的PLMN相关配置信息，包含但不限于：PLMN的类型信息及各PLMN所占的资源配额信息；
-该UP所支持的slice相关配置信息，包含但不限于：slice的类型信息及各slice所占的资源配额信息；
-该UP所支持的SDAP和PDCP-U的版本号信息；
-该UP所支持的安全处理能力，包括但不限于加密算法、完整性保护算法及头压缩算法信息；
-对其他可选功能的支持信息，包括但不限于：是否支持duplication bearer等。
第二连接建立成功响应消息：方向：CP->UP
目标CP收到来自UP的第二建立连接请求消息后，向UP发送第二连接建立成功响应消息，该消息包括但不限于以下信息：
-目标CP的标识信息。
第二连接建立失败响应消息：方向：CP->UP
目标CP收到来自UP的第二建立连接请求消息后，向UP发送第二连接建立失败响应消息，该消息包括但不限于以下信息：
-目标CP的标识信息；
-失败原因。
示例3
图11为本公开提供的CP与UP间实现UP配置更新流程示意图。
能力更新消息：方向UP->CP
在需要进行接口配置更新时，源UP向与源UP当前保持连接的CP列表中所有CP发送能力更新消息，该消息包括但不限于以下信息：
-源UP的标识信息；
-源UP更新的能力信息。
其中，源UP更新的能力信息包括但不限于以下信元：
-源UP的带宽信息；
-源UP所支持的最大UE数目；
-源UP所支持的最大DU数目；
-源UP所连接的DU list以及源UP与各个DU之间的连接属性信息，包括但不限于：时延、带宽等信息；
-源UP所连接的CP list以及源UP与各个CP之间的连接属性信息，包括但不限于：时延、带宽等信息；
-源UP所支持的PLMN相关配置信息，包含但不限于：PLMN的类型信息及各PLMN所占的资源配额信息；
-源UP所支持的slice相关配置信息，包含但不限于：slice的类型信息及各slice所占的资源配额信息；
-源UP所支持的SDAP和PDCP-U的版本号信息；
-源UP所支持的安全处理能力，包括但不限于加密算法、完整性保护算法及头压缩算法信息；
-对其他可选功能的支持信息，包括但不限于：是否支持duplicationbearer等。
能力更新确认消息：方向CP->UP
目标CP收到来自UP的能力更新消息后，向UP发送能力更新确认消息，该消息包括但不限于以下信息：
-目标CP的标识信息。
能力更新失败消息：方向：CP->UP
目标CP收到来自UP的能力更新消息后，向UP发送能力更新失败消息，该消息包括但不限于以下信息：
-目标CP的标识信息；
-失败原因。
本公开实施例还提供了一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令；所述计算机可执行指令被执行后，能够实现前述的一个或多个技术方案提供的连接方法或配置更新方法。
本实施例提供的计算机存储介质可为各种类型的存储介质，例如，只读存储介质、闪存、随机存储介质等。在一些实施例中，所述计算机存储介质可包括非瞬间存储介质。
本公开中，各个实施例中的技术特征，在不冲突的情况下，可以组合在一个实施例中使用。每个实施例仅仅是本公开的最优实施方式，并不用于限定本公开的保护范围。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现，相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本公开不限制于任何特定形式的硬件和软件的结合。
以上所述仅为本公开的示例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (16)

  1. 一种连接方法，其中，包括：
    控制面设备向用户面设备发送第一建立连接请求消息，其中，所述第一建立连接请求消息包括控制面设备信息；
    用户面设备向控制面设备发送第一连接建立成功响应消息或第一连接建立失败响应消息，其中，所述第一连接建立成功响应消息包括用户面设备信息，所述第一连接失败响应消息包括用户面设备信息及连接建立失败原因。
  2. 根据权利要求1所述的连接方法，其中，所述控制面设备信息包括以下任意一项或其任意组合：
    控制面设备名称；
    控制面设备用于建立与用户面设备的接口的1个或多个网际协议地址信息。
  3. 根据权利要求1所述的连接方法，其中，所述用户面设备信息包括以下任意一项或其任意组合：
    用户面设备名称；
    用户面设备用于建立与控制面设备的接口的1个或多个网际协议地址信息；
    用户面设备的能力信息。
  4. 根据权利要求3所述的连接方法，其中，所述用户面设备的能力信息包括以下任意一项或其任意组合：
    所述用户面设备的带宽信息；
    所述用户面设备支持的最大用户设备数目；
    所述用户面设备支持的最大分布式处理单元数目。
  5. 根据权利要求4所述的连接方法，其中，所述用户面设备的带宽信 息包括所述用户面设备支持的数据速率及频段带宽信息。
  6. 根据权利要求3所述的连接方法，其中，所述用户面设备的能力信息还包括以下任意一项或其任意组合：
    所述用户面设备连接的分布式处理单元信息；
    所述用户面设备连接的控制面设备信息；
    所述用户面设备支持的公共陆地移动网络配置信息；
    所述用户面设备支持的网络切片配置信息；
    所述用户面设备支持的简单分布式文件传输系统访问协议和用于用户面数据的分组数据汇聚协议的版本号信息；
    所述用户面设备支持的安全处理能力信息。
  7. 根据权利要求6所述的连接方法，其中，所述用户面设备连接的控制面设备信息包括以下任意一项或其任意组合：用户面设备连接的控制面设备列表，所述用户面设备与各个控制面设备之间的连接属性信息。
  8. 根据权利要求7所述的连接方法，其中，所述连接属性信息包括以下任意一项或其任意组合：
    连接的带宽；
    支持的速率；
    连接延迟。
  9. 根据权利要求6所述的连接方法，其中，所述用户面设备支持的安全处理能力信息包括以下任意一项或其任意组合：所述用户面设备支持的加密算法、完整性保护算法及头压缩算法信息。
  10. 根据权利要求6所述的连接方法，其中，所述用户面设备的能力信息还包括所述用户面设备支持的功能信息，所述功能信息包括以下任意一项或其任意组合：
    是否支持复制承载能力信息；
    是否支持分叉承载能力信息；
    是否支持辅小区分叉承载能力信息；
    支持的无线接入技术类型；
    是否支持新无线分组数据汇聚协议能力信息；
    是否支持巨型帧信息。
  11. 一种连接方法，其中，包括：
    用户面设备向控制面设备发送第二建立连接请求消息，所述第二建立连接请求消息包括用户面设备信息；
    控制面设备向用户面设备发送第二连接建立成功响应消息或第二连接建立失败响应消息，所述第二连接建立成功响应消息包括控制面设备信息，所述第二连接失败响应消息包括控制面设备信息及连接建立失败原因。
  12. 一种配置更新方法，其中，包括：
    用户面设备向控制面设备发送能力更新消息，所述能力更新消息包括用户面设备信息；
    控制面设备向用户面设备发送能力更新确认消息或能力更新失败消息，所述能力更新确认消息包括控制面设备信息，所述能力更新失败消息包括控制面设备信息及能力更新失败原因。
  13. 一种控制面设备，其中，所述控制面设备包括处理器、存储器及通信总线；
    所述通信总线配置为实现处理器和存储器之间的连接通信；
    所述处理器配置为执行存储器中存储的连接程序，以实现以下步骤：
    向用户面设备发送第一建立连接请求消息，所述第一建立连接请求消息包括控制面设备信息；
    接收来自用户面设备的第一连接建立成功响应消息或第一连接建立失败响应消息，所述第一连接建立成功响应消息包括用户面设备信息，所述 第一连接失败响应消息包括用户面设备信息及连接建立失败原因。
  14. 一种用户面设备，其中，所述用户面设备包括处理器、存储器及通信总线；
    所述通信总线配置为实现处理器和存储器之间的连接通信；
    所述处理器配置为执行存储器中存储的连接程序，以实现以下步骤：
    向控制面设备发送第二建立连接请求消息，所述第二建立连接请求消息包括用户面设备信息；
    接收来自控制面设备的第二连接建立成功响应消息或第二连接建立失败响应消息，所述第二连接建立成功响应消息包括控制面设备信息，所述第二连接失败响应消息包括控制面设备信息及连接建立失败原因。
  15. 一种用户面设备，所述用户面设备包括处理器、存储器及通信总线；
    所述通信总线配置为实现处理器和存储器之间的连接通信；
    所述处理器配置为执行存储器中存储的连接程序，以实现以下步骤：
    向控制面设备发送能力更新消息，所述能力更新消息包括用户面设备信息；
    接收来自控制面设备的能力更新确认消息或能力更新失败消息，所述能力更新确认消息包括控制面设备信息。
  16. 一种计算机存储介质，所述计算机存储介质存储有计算机可执行指令；所述计算机可执行指令被执行后，能够实现权利要求1至10、11或12提供的方法。
PCT/CN2018/096513 2017-08-10 2018-07-20 连接方法、配置更新方法、控制面设备和用户面设备 WO2019029342A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
KR1020207003724A KR102244573B1 (ko) 2017-08-10 2018-07-20 연결 방법, 구성 업데이팅 방법, 제어 평면 디바이스, 및 사용자 평면 디바이스
EP22172636.7A EP4120790B1 (en) 2017-08-10 2018-07-20 Connection methods, control plane device and user plane device
DK18844617.3T DK3668255T3 (da) 2017-08-10 2018-07-20 Forbindelsesfremgangsmåder, kontrolplanindretning og brugerplanindretning
EP18844617.3A EP3668255B1 (en) 2017-08-10 2018-07-20 Connection methods, control plane device, and user plane device
JP2020505362A JP6944041B2 (ja) 2017-08-10 2018-07-20 接続方法、構成更新方法、制御プレーンデバイス、およびユーザプレーンデバイス
US16/741,503 US11044599B2 (en) 2017-08-10 2020-01-13 Connection method, configuration updating method, control plane device, and user plane device
US17/348,205 US11540114B2 (en) 2017-08-10 2021-06-15 Connection method, configuration updating method, control plane device, and user plane device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710682460.0 2017-08-10
CN201710682460.0A CN109548038B (zh) 2017-08-10 2017-08-10 一种连接方法、配置更新方法、控制面设备和用户面设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/741,503 Continuation US11044599B2 (en) 2017-08-10 2020-01-13 Connection method, configuration updating method, control plane device, and user plane device

Publications (1)

Publication Number Publication Date
WO2019029342A1 true WO2019029342A1 (zh) 2019-02-14

Family

ID=65272730

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/096513 WO2019029342A1 (zh) 2017-08-10 2018-07-20 连接方法、配置更新方法、控制面设备和用户面设备

Country Status (8)

Country Link
US (2) US11044599B2 (zh)
EP (2) EP4120790B1 (zh)
JP (1) JP6944041B2 (zh)
KR (1) KR102244573B1 (zh)
CN (2) CN112867037A (zh)
DK (1) DK3668255T3 (zh)
FI (1) FI4120790T3 (zh)
WO (1) WO2019029342A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4007346A4 (en) * 2019-07-29 2023-01-11 NEC Corporation MASTER NODE, SECONDARY NODE AND METHOD THEREOF
KR102157103B1 (ko) * 2020-02-27 2020-09-17 제주한라대학교산학협력단 오크통을 이용한 커피의 제조 방법
CN117014297A (zh) * 2022-04-28 2023-11-07 华为技术有限公司 用户面管理方法、控制面设备及用户面设备

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1757047A1 (en) * 2004-06-29 2007-02-28 Samsung Electronics Co., Ltd. Method and apparatus for transmitting/receiving control message related to packet call service in an ip multimedia subsystem
CN103716885A (zh) * 2012-09-28 2014-04-09 电信科学技术研究院 一种本地承载管理方法及设备
CN106100800A (zh) * 2016-08-22 2016-11-09 广东工业大学 一种基于lte的物联网数据传输方式的切换方法
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统
CN106576217A (zh) * 2014-07-03 2017-04-19 康维达无线有限责任公司 用于支持多种传输机制的网络的应用数据传递服务
CN106686622A (zh) * 2015-11-09 2017-05-17 中兴通讯股份有限公司 一种网关信息更新方法及装置
CN106686666A (zh) * 2015-11-09 2017-05-17 中兴通讯股份有限公司 一种网关信息更新的方法及装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015115776A1 (en) * 2014-01-28 2015-08-06 Samsung Electronics Co., Ltd. Multistage beamforming of multiple-antenna communication system
US9332480B2 (en) 2014-03-28 2016-05-03 Qualcomm Incorporated Decoupling service and network provider identification in wireless communications
CN104410976B (zh) * 2014-11-17 2017-10-13 浙江工业大学 一种分布式端到端用户和蜂窝网络用户关联及时间分配方法
US10171136B2 (en) * 2015-05-14 2019-01-01 Lg Electronics Inc. Reducing internal signaling burden in the distributed antenna system
US11026142B2 (en) * 2016-01-20 2021-06-01 Qualcomm Incorporated Techniques for providing uplink-based mobility
CN105827528B (zh) * 2016-04-17 2019-03-26 国网四川省电力公司乐山供电公司 一种适用于频谱灵活光网络的路由选择方法
WO2018082070A1 (zh) * 2016-11-04 2018-05-11 华为技术有限公司 一种数据报文处理方法及控制面网元、用户面网元
US10499376B2 (en) * 2017-06-16 2019-12-03 Kt Corporation Methods for managing resource based on open interface and apparatuses thereof
JP6564827B2 (ja) * 2017-09-28 2019-08-21 株式会社Ｎｔｔドコモ ネットワークノード及び通信システム
US11678388B2 (en) * 2017-11-16 2023-06-13 Telefonaktiebolaget Lm Ericsson (Publ) Bearer setup and establishment using tunnel endpoint identifiers (TEIDs)
CN109995553B (zh) * 2017-12-29 2022-03-25 华为技术有限公司 一种通信方法，设备及其系统
US11412554B2 (en) * 2018-05-10 2022-08-09 Apple Inc. E1 interface setup in NG-RAN

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1757047A1 (en) * 2004-06-29 2007-02-28 Samsung Electronics Co., Ltd. Method and apparatus for transmitting/receiving control message related to packet call service in an ip multimedia subsystem
CN103716885A (zh) * 2012-09-28 2014-04-09 电信科学技术研究院 一种本地承载管理方法及设备
CN106576217A (zh) * 2014-07-03 2017-04-19 康维达无线有限责任公司 用于支持多种传输机制的网络的应用数据传递服务
CN106686622A (zh) * 2015-11-09 2017-05-17 中兴通讯股份有限公司 一种网关信息更新方法及装置
CN106686666A (zh) * 2015-11-09 2017-05-17 中兴通讯股份有限公司 一种网关信息更新的方法及装置
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统
CN106100800A (zh) * 2016-08-22 2016-11-09 广东工业大学 一种基于lte的物联网数据传输方式的切换方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
FI4120790T3 (fi) 2024-01-31
JP6944041B2 (ja) 2021-10-06
JP2020529774A (ja) 2020-10-08
CN112867037A (zh) 2021-05-28
EP4120790B1 (en) 2023-12-27
EP4120790A1 (en) 2023-01-18
EP3668255A4 (en) 2020-07-22
US20210314767A1 (en) 2021-10-07
KR102244573B1 (ko) 2021-04-26
CN109548038B (zh) 2020-12-29
DK3668255T3 (da) 2023-03-13
KR20200024315A (ko) 2020-03-06
US11540114B2 (en) 2022-12-27
EP3668255B1 (en) 2023-02-22
CN109548038A (zh) 2019-03-29
EP3668255A1 (en) 2020-06-17
US20200154268A1 (en) 2020-05-14
US11044599B2 (en) 2021-06-22

Similar Documents

Publication Publication Date Title
US11558916B2 (en) Method and apparatus for establishing dual-connectivity to transmit data in new radio communication architecture
US11943827B2 (en) Method and apparatus for establishing dual-connectivity to transmit data in new radio communication architecture
KR102407078B1 (ko) 사용자 정보 관리를 위한 방법 및 시스템
US11540114B2 (en) Connection method, configuration updating method, control plane device, and user plane device
US11765787B2 (en) Entity configuration method, device and system, and CU-U
WO2021097858A1 (zh) 一种通信方法及装置
WO2019033905A1 (zh) 数据流传输安全控制方法及装置
US11382152B2 (en) Method and device for configuring GTP transmission channel and storage medium
CN101815358A (zh) 一种用户设备之间的数据传输方法
KR102480610B1 (ko) 주소 송신 방법, 장치 및 저장매체
WO2019029255A1 (zh) 密钥、参数发送方法及装置、用户面实体、控制面实体
WO2022047749A1 (zh) 通信方法及装置
WO2022082683A1 (zh) 一种用于接入回传一体化iab系统中的通信方法及相关设备
EP4213418A1 (en) Interface security protection method and device

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020505362

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20207003724

Country of ref document: KR

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

Country of ref document: EP

Effective date: 20200310